The source control component of the Jazz™ technology platform manages the source
code, documents, and other artifacts that a team creates. It provides
change-flow management to facilitate the sharing of controlled artifacts,
retains a history of changes made to these artifacts, and enables
simultaneous development of multiple versions of shared artifacts,
so that teams can work on several development lines at the same time.
A software development team typically works with a large base of
files that comprises the source code for a software product or system.
As a team member, you work within this base of source code, changing
file content to add new features or fix defects. After you verify
that your changes are correct (by building and testing the code in
a private workspace, for example), you share the changes with the
rest of the team, whose members have also been changing files, including
some on which your work depends. Rational Team Concert™ source
control organizes "versionable" items (files and folders) into components
and streams, and provides workspaces where you can view and modify
file and folder contents. Together, these repository objects represent
the configuration of the system being developed, and allow any configuration
to be retrieved, shared, or built. They organize a team's files, track
and share changes, and keep the entire team working in concert to
achieve common goals.
Rational Team
Concert source control is closely integrated with the other application
development lifecycle tools included in Rational Team Concert.
- The Jazz Build Engine and
Build System Toolkit have built-in support for loading files from Rational Team Concert source
control, capturing snapshots of build input so that a build can be
reproduced exactly, and provides direct access to a rich set of tools
that you can use to view the component versions that are present in
a specific build and compare them with versions in other builds, streams,
and workspaces.
- Change sets can be linked to work items so that you can trace
individual changes and get insight into why they were made. For more
information, see Tracking work items.
- Use process preconditions to control the flow of change sets.
For example, you can configure a process so that a change set must
be reviewed and approved before it can be delivered to an integration
stream. For more information, see Working with projects, teams, and process.