Tip:
Highlight text to annotate it
X
An overview of Jazz source control, which manages the source code, documents, and other artifacts that a team creates.
Jazz source control manages the source code, documents, and other artifacts that a
team creates. It provides change-flow management to facilitate sharing, retains a history of changes made, and enables the
simultaneous development of multiple versions of shared artifacts, so that teams can work on several development lines at the
same time. Jazz source control also integrates with other Rational Team Concert components, such as builds and work items,
and with other source control products, such as IBM Rational ClearCase and Subversion. The basic unit of source control is a
component. A component is a collection of related files and folders, such as an Eclipse project or a group of documents that
comprise web site content. A stream is a repository object that includes one or more components. A repository workspace is an
object in the repository that stores components as versionable artifacts that you can load into your sandbox. A sandbox is a
directory on your computer’s file system where you can view and modify files and folders. A change set is a repository object
that collects a related group of changes, so that they can be applied to a stream or workspace in a single operation. Team
members create change sets by modifying files in their sandbox, then committing them to a repository workspace, which backs up
and records the changes. When team members want to share their changes with the team, they deliver their changes to a
stream. Other team members can then accept the change sets from the stream into their repository workspace. The contents of a
workspace, component, or stream can be expressed as a collection of change sets. The history of a component comprises an
ordered list of change sets, each of which includes one or more items. The history of an item in a change set comprises an ordered
list of change sets in which the item appears. A baseline is a repository object that provides a record of the state of a component in a
workspace or stream. The change history of a component includes baselines, each of which includes exactly one version of every
artifact in the component. Baselines are fixed points of reference, useful for recording a milestone or release or for initializing
streams and workspaces where new development can begin. A snapshot is a repository object that includes exactly one
baseline for each component in a stream. Snapshots are useful for capturing the state of a stream, and are typically used to record
important stream configurations so that they can be recreated. When two or more team members modify the same file, conflicts
result. These conflicts must be resolved when one team member accepts the other's changes. Jazz source control detects conflicts
and warns you about them before you accept them. Some conflicts can automatically resolve. You can prevent conflicts by locking a
file, so that it cannot be modified by other team members. Jazz source control integrates closely with other Rational Team
Concert components, such as work items and builds. With work items, you can link change sets with activities, such as feature
development and defect fixing. With builds, you can specify the repository workspace from which to build. Rational Team Concert
supports interoperation between Jazz source control and Rational ClearCase. A synchronization process retrieves changes
created in Jazz source control and checks them in to Rational ClearCase as new versions. It also retrieves changes created in
Rational ClearCase and delivers them to a Jazz source control stream called a ClearCase Synchronized Stream. You can
use Rational Team Concert to import the contents of a Subversion repository to one or more Jazz source control components. If you
install a Subversion client for Eclipse into Rational Team Concert, you can link Subversion revisions to work items. Jazz
source control allows you to store, retrieve and share source code and other artifacts. Jazz source control also integrates closely
with other Rational Team Concert components, such as builds and work items and supports integration with other products,
such as Rational ClearCase and Subversion.