Use the CrossPlatformBuild record to promote a successful build

In the previous step, you learned how to use a CrossPlatformBuild record to rerun a failed build until the build succeeded. The next step is to learn how to use the same record to promote a successful build. Before you can promote the build, the CrossPlatformBuild record used must be in the BuildCompleted state.
In addition, note the following distinctions:
  • In SCLM, promote refers to moving a successfully built SCLM package from one project group to another, according to a project's architecture and project definitions. An SCLM promote operation can also be thought of as the process of moving modified members of an application or of its components within the scope of a package from one level in the project hierarchy to the next. You can perform multiple promote operations on the same build as needed to move the build up your group hierarchy.
    Note: CCBuild records do not support multiple promotion levels. CCBuild records ignore any promote operations subsequent to the first one.
  • In Rational® ClearCase®, promote refers to running the Rational ClearCase command specified in the Promote Command field of a CCBuildConfig record. This command acts on the Rational ClearCase view specified in the View field of that record. Examples of possible promote operation commands in Rational ClearCase are findmerge, deliver, and customized perl scripts.
    Note: CCBuild records do not support multiple promotion levels. CCBuild records ignore any promote operations subsequent to the first one.
  1. Run a Rational ClearQuest® query on CrossPlatformBuild records.
  2. From the Results page, select the CrossPlatformBuild record needed to promote the build. The State field shows that the record is in the BuildCompleted state.
  3. Click the Apply button to accept the state changes.
  4. From the toolbar in the Details window, click the Menu button Menu button in the Details window and click Refresh to refresh the build record in the database.
  5. Do one of the following:
    • If the promote operation succeeds, the State field changes to the PromoteCompleted state. For Rational ClearCase builds, this change means either that the promote command specified in the CCBuildConfig record ran successfully without success keywords or that a success keyword was found in the output of the promote. If you run a Rational ClearCase promote operation without specifying success keywords, you can still verify that the Rational ClearCase artifacts were promoted successfully by clicking the Apply button and checking the log file <rational_root>\ClearQuest\cpscm.log. You can also verify that the files promoted successfully, based on the command that was run.
    • If the promote operation fails, the State field changes to the PromoteFailed state. Review the error messages in <rational_root>\ClearQuest\cpscm.log . See additional information about SCLM communications in <rational_root>\ClearQuest\cpscm_communications.log
    • Note that, if you promote a large SCLM job in batch mode, the steps for refreshing and modifying might not move the record from the PromotePending state because the build might never have actually been promoted. If this situation occurs, it usually means that there is an error in the JCL code. Either delete the record or, if you are a member of the Rational ClearQuest restricted group, move it to the PromoteFailed state manually and fix the problem. (For more information about this group, see Optional: Create a "restricted" Rational ClearQuest user group.)
This topic completes the procedure for using a CrossPlatformBuild record to promote a build. If your promote operation was successful, read the next topic for reference.

Feedback