02.05.2013 Views

Description - Mks.com

Description - Mks.com

Description - Mks.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

customer?<br />

If the development team has been using change packages, they can isolate the files that relate to<br />

the new data <strong>com</strong>pression feature. However, without the functionality of Apply CP and Resync CP,<br />

the buildmaster at abcBusiness would have to manually search the required change package(s)<br />

and individually review all of the associated files to isolate the changes related to the feature. The<br />

buildmaster would then have to manually add, drop, rename, and move files, update file revisions,<br />

merge around unwanted revisions, merge in required changes, and merge out any unwanted<br />

changes.<br />

Using the functionality of Apply CP and Resync CP, this <strong>com</strong>plicated process be<strong>com</strong>es largely<br />

automated. In Source Integrity, the Apply CP operation works directly in the project to add and<br />

drop files, and update file revisions as required to create the desired change. Source Integrity<br />

presents you with a list--the backfill list--of all change packages required to capture the issue. In<br />

the Apply CP operation, you must either accept or decline this list--you cannot make selections. If<br />

you accept the list, the Apply CP <strong>com</strong>mand <strong>com</strong>pletes. If you decline the list, the Apply CP<br />

<strong>com</strong>mand cannot <strong>com</strong>plete.<br />

If the Apply CP <strong>com</strong>mand fails because merging is required, you can then run the Resync CP<br />

<strong>com</strong>mand. Resync CP works in a sandbox and allows you to make selections from the backfill list.<br />

Source Integrity then merges around unwanted changes and uses differencing to merge files.<br />

Consider once again, the abcBusiness development team. Because the team has been tracking all<br />

of their changes through the use of change packages, they can target the main trunk of<br />

development and use Apply CP and Resync CP functionality to extract only those files that relate<br />

to the new data <strong>com</strong>pression feature. Those specific change packages can then be applied to a<br />

variant project of Aurora 2.0 and testing carried out within a new project designed specifically for<br />

the customer.<br />

The functionality allows you to maximize existing development work, while being more responsive<br />

to both internal and external stakeholders. Apply CP and Resync CP are especially effective in any<br />

environment where there are large numbers of files to deal with--whether these are code files for a<br />

software project or Web pages for a <strong>com</strong>plex Web site.<br />

Apply CP Example<br />

This section provides an example to show how Apply CP can be used in your environment. In this<br />

example, the buildmaster brings a new feature from the main trunk of project development and<br />

applies it to an earlier release.<br />

The abcBusiness software <strong>com</strong>pany has released their Aurora software, version 3.0. When the<br />

release was <strong>com</strong>pleted, the project was checkpointed and all project members were labelled. The<br />

development team is now working on a new set of features for the next release, 4.0. A new feature<br />

for this release is a timestamp function. All the changes associated with the timestamp function<br />

49 of 457

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!