Use the CrossPlatformBuild record to rerun a failed promote operation

Before you begin
In the previous topic, you learned how to use a CrossPlatformBuild record to promote a successful build. The final step of the tutorial is to learn how to rerun a failed promote operation. Before you can rerun a failed promote operation, the CrossPlatformBuild record used for the repromote operation must be in the PromoteFailed state.
About this task
When you rerun a promote operation from a parent record, any child builds that promoted successfully during the first promote operation are ignored. This action ensures that the states of all of the records are kept in sync with each other and with the parent record.
Note: Repromoting a build from a child record that is associated with a CrossPlatformBuild parent record causes a state change in the child record that puts it out of sync with its parent and with any siblings it might have.
  1. Run a Rational® ClearQuest® query on CrossPlatformBuild records.
  2. From the Results page, select the CrossPlatformBuild record needed to repromote the build. The State field shows that the record is in the PromoteFailed state.
  3. 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.
  4. From the toolbar in the Details window, click the arrow next to the Change State button Change State button in the Details window, and click RePromote. The State field changes from the PromoteFailed to the PromotePending state.
  5. Click the Apply button to accept the state changes.
  6. Do one of the following:
    • If the repromote 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 repromote 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.)
Results
What to do next
This topic completes the procedure for using a CrossPlatformBuild record to rerun a failed promote operation. After you successfully promote a build, you have completed the procedures in tutorial. The final topic covers a few important topics and offers some tips that were not fully addressed in the tutorial.

Feedback