Before you begin
In the previous step, you learned how to use a CrossPlatformBuild
parent record to run a build. The next step is to learn how to use the same
parent record 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.
About this task
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.
- Run a Rational® ClearQuest® query
on CrossPlatformBuild records.
- 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.
- From the toolbar in the Details window, click
the Menu button
and click Refresh to
refresh the build record in the database.
- Click the Apply button
to accept the state changes.
- From the toolbar in the Details window, click
the Menu button
and click Refresh to
refresh the build record in the database.
- 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 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.)
What to do next
This topic completes the procedure for using a CrossPlatformBuild
parent record to rerun a failed build. If you are running a build that continues
to fail, resolve any errors and rerun the build until it succeeds (until the
CrossPlatformBuild record changes to the BuildCompleted state). after you
achieve a successful build, the next step is to learn how to promote it.