Before you begin
Use a CrossPlatformBuild record to run a cross-platform build. Before
you can run a cross-platform build, the build record used must be in the Submitted
state.
Procedure
- Run a Rational® ClearQuest® query
on CrossPlatformBuild records.
- From the Results page,
select the CrossPlatformBuild record you want to run a build. In
the Details window, the State field shows that the
record is in the Submitted state.
- From the toolbar in the Details window, click
the arrow next to the Change State button
, and click Build. The State field changes from the Submitted
to the BuildPending state.
- 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 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 IBM 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.)