1. IBM Software Exercise
Developing Software with
IBM Rational Team Concert
Exercise 4: Managing Builds

2. Student Exercises
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
© Copyright IBM Corp. 2008, 2013 Exercise 4. Managing Builds in Rational Team Concert 4-1
V9.0
EXempty
Exercise 4. Managing Builds in Rational Team
Concert
What this exercise is about
The purpose of this exercise is to become familiar with the IBM® Rational
Team Concert™ build system, to request builds, and to examine build
results.
What you should be able to do
At the end of this exercise, you should be able to:
• Explore the builds in the JavaUI project.
• Request a team build for the JavaUI project.
• Compare builds.
• Optional: Request a personal build for the JavaUI project.
Requirements
Make sure that the Jazz™ build engine is running:
• If you are using the VMware image in a stand-alone lab environment, the
desktop contains a shortcut to start the Jazz build engine. Double-click
Start Jazz Build Engine. You can minimize the command window that
displays the build console output, but do not close it.
• If you are not using the default VMware lab environment, ask your
instructor for the required setup actions.

3. Student Exercises
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
4-2 Developing Software with IBM Rational Team Concert, V4.0.4 © Copyright IBM Corp. 2008, 2013
4.1. Explore the builds in the Java UI project
Scenario
In the previous exercises, a basic Eclipse build ran whenever you tested your changes by
executing the Java™ UI project. However, an audited Jazz build has been running in the
background as a scheduled build against the BRM team stream every 30 minutes. In this
exercise, you browse the build results in the JKE Banking project.
__ 1. If necessary, start Rational Team Concert. When prompted for a workspace, select
C:Workspacesdeb.
__ 2. Open the Work Items perspective.
__ 3. In the Team Artifacts view, expand
JKE Banking > Builds. Double-click the jke.dev build definition to open the Builds view. A
list of builds that were run is displayed.
__ 4. In the Builds view, double-click the most recent completed build in the list, which is listed
first. The tabbed Build Details view opens.
__ 5. In the Build Details view, examine the information on the Overview tab.
Help. The Overview tab displays high-level details of the build. For instance, the Status
Trend graphic shows the build results over the course of the project. You can click any of the
builds that are represented in the Status Trend graphic to see the details of a build.
__ 6. Click the Downloads tab. Can you open the project compressed file that this build created?
Try it.
Help. Assuming that you are looking at the Build Details view for a completed build, you can
double-click the compressed file that the build produced and then run the batch files.
__ 7. Click the Overview tab. In the Contribution Summary section, identify the work items that
are part of this build. Notice the snapshot that was created as part of the Build process.
__ 8. Explore the other tabs and the information that the Build Details view captures.

4. Student Exercises
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
© Copyright IBM Corp. 2008, 2013 Exercise 4. Managing Builds in Rational Team Concert 4-3
V9.0
EXempty 4.2. Request a team build for the JKE Banking project
Scenario
In this exercise, you request a team build for the JKE Banking project. If a shared Jazz
server and build server are being used, the instructor will demonstrate this exercise.
Because several students have delivered their completed work to the BRM team stream,
this build reflects the changes.
__ 1. In the Team Artifacts view, expand JKE Banking > Builds.
__ 2. Right-click the jke.dev build definition, and then click Request Build. A Request Build
window opens.
__ 3. Click Submit.
Help. After you click Submit, the focus shifts to the Builds view. The status in the Progress
Column for this build is Pending.
__ 4. While the build is running, refresh the Builds view every few seconds to monitor progress.
__ 5. When the build is complete, double-click the new build at the top of the Builds view.
Examine the build results and make sure that the build is complete.
__ 6. Run the JKE application that you built:
• In the Build Details view, click the Downloads tab.
• Select jke-java-<<build info>>.zip and click Save As to save the file to the desktop.
• Extract the compressed file to the desktop.
• Start the server for the application by running the jke.server.windows.bat file.
• Start the client by running the jke.client.windows64.bat file.
Help. This build was completed in the build.jke.dev Workspace, which flows with the BRM
stream. Because student changes were delivered to this stream, the changes are included
in this build.
__ 7. Close both of the application windows.

5. Student Exercises
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
4-4 Developing Software with IBM Rational Team Concert, V4.0.4 © Copyright IBM Corp. 2008, 2013
4.3. Compare builds
Scenario
In this exercise, you compare the contents of the most recent completed build on the BRM
team stream to a build that was completed before the lab exercises began. By comparing
builds, you can see which work items were completed and what the scope of source file
changes were between the builds. You can even navigate to see the file-level changes that
were made between builds.
__ 1. In the Team Artifacts view, expand JKE Banking > Builds.
__ 2. Double-click the jke.dev build definition to open the Builds view.
__ 3. Choose builds to compare:
• Select the most recently completed build in the Builds view.
• While pressing the Ctrl key, select the I20130729-04460 build. This build is the build that
was completed before you started the exercises.
• Right-click one of the selected builds, and then click Compare Builds.
Help. Use the build that you completed in the previous exercise.
__ 4. In the Change Explorer view, expand all of the folders and subfolders.
Help. Below the Java UI Component element is a folder for each work item change set that
contributed to the most recent build. Who delivered each change set? What information do
you find if you continue to navigate into the subfolders for each change set?
__ 5. In one of the change sets, select one of the Java source files. Right-click the file, and then
click Open in Compare Editor.
Help.The changes to this file are highlighted in the Compare Editor window.

6. Student Exercises
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
© Copyright IBM Corp. 2008, 2013 Exercise 4. Managing Builds in Rational Team Concert 4-5
V9.0
EXempty 4.4. Exercise 4.4: Request a personal build
Scenario
Recall that when you tested changes to the JKE Banking application in the previous
exercise, you built and ran the application by using an Eclipse build. In this scenario, you
request a Jazz build using the BRM Team Integration definition, but you override the defined
repository workspace for the build and use a personal workspace instead. Personal builds
are useful for testing changes in your personal workspace by using the defined build script
for the project before delivering work to the shared stream. These personal builds are often
called “preflight” builds.
__ 1. In the Team Artifacts view, expand JKE Banking > Builds.
__ 2. Right-click the jke.dev build definition, and then click Request Build.
__ 3. Complete a Jazz build in your personal repository workspace:
• Expand Build Options. Select the Personal Build check box.
• Next to Repository workspace, click Browse.
• Select Deb BRM Stream Workspace, and then click OK.
• Click Submit.
Help. Normally, you build the JKE Banking application with your personal changes as a
preflight check or verification step before you deliver your changes into the shared stream
for the project.
Observe that only your loaded workspaces are available to run a personal build.
__ 4. After the build is finished, examine the build results and test the application.
End of exercise