Using Resync CP in Your Development Environment
This section provides an example to show how Resync CP can be used in your environment. The example also illustrates how Resync By CP can be used in a developer’s Sandbox.
The development of a new release typically involves working on hundreds of files that span many Integrity Lifecycle Manager projects. Whenever a fix is made, or a feature added, it may require the manipulation of a single file, or many different files across multiple projects. A fix or new feature may also include new dependencies within the source code.
If developers resynchronize only a single file into their Sandboxes, their builds may break because of new dependencies in the code. Such broken builds cause delays and prevent the team from completing their work on time. However, it is possible to avoid this lost time by using the Resync CP command.
Resync CP allows developers to specify a change package and have all changes associated with that change package resynchronized into their Sandboxes. The commands save development time because they:
• automatically search for the required files
• determine what other change packages the selection is dependant on (this is known as the backfill list) and also resynchronize those change packages into the Sandbox
If the developer is working on a file conflict, Resync CP also merges new information into a file. The merge operation ensures that the Sandbox is up-to-date and that no changes are lost.
The Resync CP command also allows a developer to remove a bug fix or feature that is incomplete or not working.