IBM Rational ClearCase and IBM Rational ClearQuest Evaluation Guide, Part 1: Unified Change Management

Page 5 of 8  Document options PDF - Fits A4 and Letter 61 KB Get Adobe® Reader® My developerWorks needs you! Connect to your technical community Rate this tutorial Help us improve this content

Unified Change Management: Release engineer role

Recommending the latest baseline

Now that there is a new baseline, you would like to update your development stream so that you are working with the latest version of your application. This will minimize the chance that any new work you perform will conflict with activities already delivered to the Integration stream. You also want other members of your team to be up to date with the latest changes from the integration stream. You will now take on the final role of today's exercise – Chris, the release engineer. Before Chris builds the software to be released, he needs to be sure that his workspace is current with the latest, recommended baseline. (Refer to the section: "Join a UCM project," above.)

1. Navigate back to the ClearCase Navigator window.
2. Join the UCM project again, but login this time as chris/chris. You may need to de-select the checkbox Reuse exisiting connection. Be sure to create a new development view, but don't create an integration view. Use the default names.
3. Load the CLSICS_comp1 VOB into the newly created view.
4. Navigate to Readme.html and open a version tree. NOTE: Your view is selecting an older version of the file. Close the version tree.
5. Open Readme.html. NOTE: You still see the spelling error.
6. Navigate back to the Metadata explorer.

Now you should recommend this baseline to your developers, as the foundation for any future work within their development streams. Recommending a baseline ensures that your teams know what is the latest, most stable baseline in the project.

7. Right-click on the integration stream again and select Recommend Baselines.

8. Under Filter Promotion Level, select BUILT from the pull-down menu and click the Fetch Baselines button.

9. Ensure that QA_Rel_15 appears under the column Baseline to Recommend, and click OK.
10. Close the Metadata Explorer windows.

Now that we have a "built" baseline that is recommended, we want to rebase our stream to get those changes in our workspace.

Much like the deliver operation, ClearCase identifies changes in the latest baseline that are not visible in your view, and performs merges where needed.

1. Click on the new view you created for Chris. From the ClearCase menu, select Rebase.

2. Click the Advanced button and confirm that you are rebasing the newly recommended baseline. Click OK.

3. Login to ClearQuest as username/password chris/chris.
4. Click OK to acknowledge the rebase.
5. Click Complete Rebase.
6. Close the rebase confirmation window.

In this case, all of these merges are completed automatically and you choose to Complete the Rebase operation. You now have a stable configuration in your workspace that you can build and release to production.

7. Double-click Readme.html and verify the correction. Note that the changes made during the merge to the integration stream are now visible in your private development stream.
8. Now open a version tree and review the flow of the changes made.

Back to top

Conclusion

By now, you have seen how Rational ClearCase and Rational ClearQuest can benefit different members of your software development team.

The Project Lead:

• Is able to organize and manage the project
• Can accurately assess project status
• Can intelligently evaluate resources and assign change requests

The Developer:

• Can easily focus on assignments
• Can quickly create isolated environments in which to make changes
• Can deliver changes and makes those changes automatically available to the team

The Integrator:

• Can easily focus on assignments using custom queries
• Can easily update project status
• Can quickly create baselines and track the promotion level of those baselines

Back to top

	Page 5 of 8