Rerunning a cross-platform build

Use the same CrossPlatformBuild record used to run a build to rerun a failed build.
Before you rerun a failed build, the CrossPlatformBuild record used must be in the BuildFailed state.

In addition, you should resolve the errors that caused the build to fail before attempting a rebuild. Reference the log files <rational_root>\ClearQuest\cpscm.log and <rational_root>\ClearQuest\cpscm_communications.log.

When you rerun a build from a parent record, any child builds that ran successfully during the first run are ignored. Ignoring successful child builds ensures that the states of all of the records are kept in sync with each other and with the parent record.
Note: Rerunning a build from a child 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 with which to rerun the build. The State field shows that the record is in the BuildFailed state.
  3. 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 ReBuild. The State field changes from the BuildFailed to the BuildPending state.
  4. Click the Apply button to accept the state changes.
  5. 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.
  6. 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.
  7. Do one of the following:
    • If the build succeeds, the State field changes to the BuildCompleted state. For Rational ClearCase® builds, this change means either that the build command specified in the CCBuildConfig record ran successfully without success keywords or that a success keyword was found in the build output. If you run a Rational ClearCase build without specifying success keywords, verify that the Rational ClearCase artifacts built successfully by clicking the Apply button and checking the log file <rational_root>\ClearQuest\cpscm.log. You can also verify that the files built successfully, based on the command that was run.
    • If the build operation fails, the State field changes to the BuildFailed 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 run a large SCLM job in batch mode, the steps for refreshing and modifying might not move the record from the BuildPending state because the build might never have actually run. If the build does not run, 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 BuildFailed state manually and fix the problem. (For more information about this group, see Optional: Create a "restricted" Rational ClearQuest user group.)

Feedback