Component baselines

A baseline represents a configuration of a component at any particular point in time. Baselines serve as fixed points of reference, and are useful both for initializing streams and workspaces that pick up from a given point of a set of components, and for sharing the changes to components at a granularity coarser than that of their individual change sets.

A baseline is a repository object that provides an immutable record of the configuration of a component in a particular workspace or stream. The component's configuration is determined by the change sets that have been delivered to it. Baselines are fixed points of reference, which are useful for reverting a component to an earlier configuration, or for initializing streams and workspaces where new development can begin, starting with the configuration that the baseline has recorded.

A baseline consists of one or more change sets. Delivering or accepting a baseline effectively delivers or accepts all of the change sets in it.

A baseline saves the state of a component in a workspace so that you can restore that state when needed. A baseline represents the configuration of a component at a given point in time. Baselines are numbered automatically (in monotonically increasing order) when created. You can also give a baseline a name and a description.

A snapshot includes one baseline for each component in a workspace or stream.


video icon Watch videos

CLM playlist
Jazz.net channel
User Education channel

learn icon Learn more

CLM learning circle
Agile learning circle
Learning circles

ask icon Ask questions

Jazz.net forum
developerWorks forums

support icon Get support

Support Portal
Deployment wiki
Support blog