Overview of Rational Team Concert source control
A software development team typically works with a large base of files that comprise the source code for a software product or system. As a team member, you can add new features or fix existing ones within this base of source code. After you build and test the code to verify that your changes are correct, you can share the changes with the rest of the team. 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 files for a team, and track and share changes so that the entire team can work simultaneously to achieve common goals.
- The Jazz Build Engine and Build System Toolkit have
built-in support for loading files from Rational Team Concert source
control,
and capturing snapshots of build input so that a build can be reproduced
exactly. It also provides direct access to a rich set of tools that
you can use to view the component versions in a specific build and
compare them with versions in other builds, streams, and workspaces.
For more information, see Building with Rational Team Concert Build.
- Change sets can be linked to work items, which support traceability
of individual changes and insight into the reasons why they were made.
For more information, see Tracking work by using work items.
- Process preconditions can be used 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 Administering change and configuration management projects.
- The repository
Rational Team Concert source control uses a secure repository that is hosted on a server and accessed by clients through a URL. The repository stores objects such as streams, work items, and workspaces that help manage change flow. It also stores controlled artifacts that represent and can be retrieved as files or folders in a file system. - Workspaces and sandboxes
A workspace is an area where you can view or modify components. A repository workspace on the server stores components as versionable artifacts that can be loaded into a sandbox on the client, such as an Eclipse workspace or an ordinary folder. - File content types and line delimiters
When your team develops software on more than one platform, differences in platform conventions for line delimiters (line termination characters) in text files can affect content merges and other development tasks. Rational Team Concert source control stores text files in a normalized format. It also allows users to specify the line delimiter and MIME type properties on files. - Read access permissions
Owners and administrators can change the read access permissions for streams, repository workspaces, components, and files and folders. If a component or stream is owned by a team or project area, the process area permissions determine who can set read access permissions. - Creating custom attributes
You can create custom attributes on source file versions, streams, snapshots, components, and baselines. You define custom attributes in the project area. You can query for custom attributes from the command line interface. - Streams and components
A stream is a repository object that includes one or more components. A component is a collection of related artifacts, such as a set of related Eclipse plug-ins or a group of documents that comprise website content. - Change sets and change flow
A change set is a repository object that collects a related group of file, folder, and symbolic link modifications within a component. Change sets flow between repository workspaces and streams. The workspace's flow targets specify the sources and destinations of incoming and outgoing change sets.
|
Jazz.net channel User Education channel |
Agile learning circle Learning circles |
developerWorks forums |
Deployment wiki Support blog |
