• Save
Module 4: Working with Builds
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
531
On Slideshare
531
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Contents
    Module overview 4-2
    Rational Team Concert build system architecture4-3
    Developer build activities4-6
    Monitoring team builds4-11
    Compare builds4-21
    Module summary 4-23
    Exercise 44-24
  • Notes:
    Instructor notes:
    Purpose — List the unit objectives
    Details —
    Additional information —
    Transition statement —
  • Instructor Notes:
    Explain where you are in the course.
  • Build-engine objects:
    Collect build requests, give requests to build computers that poll for requests, and manage results
    Receive and store build requests from developers
    Receive status reports from build engines during build execution
    Store build execution results that the build engines return
    Build computers:
    Generate builds that Jazz™ Team Server dispatches
    Poll Jazz Team Server for build requests
    Run build scripts
    Report build status and results to Jazz Team Server
  • Instructor Notes:
    Explain where you are in the course.
  • Instructor Notes:
    Explain where you are in the course.
  • Instructor Notes:
    Explain where you are in the course.
  • Comparing builds is a useful diagnostic tool to pinpoint which change or changes caused the behavior of your application to change. Suppose you generated a build yesterday, and the application performed correctly. After the build today, however, the application stops responding when you try to use a specific function. You can compare the two builds to identify the work items that were included in current build that were not in yesterday’s build. From the change set information in each work item, you can identify the file-level differences between the two builds. In all likelihood, the cause of the problem in the build today was introduced in those file-level changes.
  • Notes:
    Instructor notes:
    Purpose — Summarize the unit
    Details —
    Additional information —
    Transition statement —
  • Instructor Notes:
    This lab takes approximately 15 minutes to complete.

Transcript

  • 1. Accelerating Product and Service Innovation Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 9.0 Developing Software with IBM Rational Team Concert Module 4: Working with Builds © Copyright IBM Corporation 2008, 2014
  • 2. Unit objectives After completing this unit, you should be able to: • Describe the IBM® Rational Team Concert™ build system • Generate a build by using Rational Team Concert • Monitor Rational Team Concert public builds • Compare builds © Copyright IBM Corporation 2008, 2013
  • 3. Rational Team Concert build systme architecture > Rational Team Concert build system architecture Developer build activities Monitoring team builds Comparing builds > = Current topic © Copyright IBM Corporation 2008, 2013
  • 4. Jazz Team Build system architecture Developer (client) Developer (client) Developer (client) Release engineer Build engine object Build engine object Build engine object Build machine Build machine Build machine Jazz™ Team Server Repository Build computers © Copyright IBM Corporation 2008, 2013
  • 5. Jazz database build objects The build definition defines the build script and other properties that specify how the build is invoked. The build definition also provides this information:  The build schedule for automated builds  The workspace to build from The build engine represents a process on a build computer that polls the repository for build requests. The build request represents a request to run a build, as specified by the selected build definition, on the next available build engine. The build result contains the output from a build, such as execution summaries, logs, and properties. © Copyright IBM Corporation 2008, 2013
  • 6. Developer build activities  Rational Team Concert build system architecture > Developer build activities  Monitoring team builds  Comparing builds > = Current topic © Copyright IBM Corporation 2008, 2013
  • 7. Jazz Team Build roles and actions Develop/Obtain a build script Release engineer Developer Create workspace Create build definitions Create build engine objects Monitor build engines Set up build machine Request a build Monitor build status View build results Compare builds Develop or obtain build script © Copyright IBM Corporation 2008, 2013
  • 8. Developer role: Build actions Request a build  Request builds from the Builds view, which you can access from the Team Artifacts view  Request public or personal builds Monitor the status of builds  Monitor status in the Builds view Query available builds Inspect completed builds  Identify and retrieve the artifacts that are produced Compare builds © Copyright IBM Corporation 2008, 2013
  • 9. Requesting a build Request Build © Copyright IBM Corporation 2008, 2013
  • 10. Build options: Personal builds You can select the workspace for the build. The team is not notified of the build result. Typically, use personal builds to test changes before you deliver them to the team. Select Build Engine. Select Workspace. Expand Build Options. Select Personal Build. © Copyright IBM Corporation 2008, 2013
  • 11. Monitoring team builds  Rational Team Concert build system architecture  Developer build activities > Monitoring team builds  Compare builds > = Current topic © Copyright IBM Corporation 2008, 2013
  • 12. Monitoring builds Cancel  Removes pending build requests from the queue Abandon  Removes in-progress stalled builds from the queue Build Completion  Progress indicates completion © Copyright IBM Corporation 2008, 2013
  • 13. Monitoring builds (continued) Estimated time Real-time progress Build label Build definition Actual time TagsStart time Status © Copyright IBM Corporation 2008, 2013
  • 14. Build results review: Summary © Copyright IBM Corporation 2008, 2013
  • 15. Build results review: Activities © Copyright IBM Corporation 2008, 2013
  • 16. Build results review: Compilation © Copyright IBM Corporation 2008, 2013
  • 17. Build results review: Downloads © Copyright IBM Corporation 2008, 2013
  • 18. Build results review: Logs © Copyright IBM Corporation 2008, 2013
  • 19. Build results review: Properties © Copyright IBM Corporation 2008, 2013
  • 20. What is the purpose of the automatic snapshot that is taken during a build ? Why would you generate a personal build ? Discussion © Copyright IBM Corporation 2008, 2013
  • 21. Comparing builds  Rational Team Concert build system architecture  Developer build activities  Monitoring team builds > Comparing builds > = Current topic © Copyright IBM Corporation 2008, 2013
  • 22. Comparing builds Comparing builds provides a way to examine the differences in content between two versions of your application.  Which work items are implemented in one build and not the other?  For those work items, which source files were modified? Builds can be compared with other builds or with the contents of a repository workspace or stream.  Compare a build with a repository workspace or stream.  Compare two builds.  Compare a build with the latest available in a stream.  Compare a build with its previous build. © Copyright IBM Corporation 2008, 2013
  • 23. Unit summary Having completed this unit, you should be able to: • Describe the IBM® Rational Team Concert™ build system • Generate a build by using Rational Team Concert • Monitor Rational Team Concert public builds • Compare builds © Copyright IBM Corporation 2008, 2013
  • 24. Exercise 4: Managing builds in Rational Team Concert Complete these tasks:  Browse builds in the Conversion team area.  Request a team build.  Compare builds.  Request a personal build. © Copyright IBM Corporation 2008, 2013