Overview of Engineering Workflow Management source control

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 sharing of controlled artifacts, retains a history of changes made to these artifacts, and supports 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 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. Engineering Workflow Management 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.

Engineering Workflow Management source control is closely integrated with the other application development lifecycle tools included in Engineering Workflow Management.
  • The Jazz Build Engine and Build System Toolkit have built-in support for loading files from Engineering Workflow Management 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 Working with builds in 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.

License note: To perform the task described here, you must be assigned the Developer Client Access License.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki