About changesets

A changeset is a logical grouping of changes that is created automatically every time you deliver changes to a stream or project in a repository.

Changesets overview

Each changeset creates a new version of a stream or project. Changesets give insight into the development activity in your streams and enable you to easily identify changes. They reduce the complexity of parallel development by making it easier to manage sets of changes.

Note: Use PulseUno to create chains of plugins and configure changesets to automatically create reviews and run chains. For details, see the PulseUno online help. You can use PulseUno functionality only if it is enabled in your database.

The following diagram illustrates multiple streams where each circle represents a new stream version when a delivery has been made. Changeset version #0 (zero) is empty and represents the initial state of a stream or project.

multiple_streams_versions.fw.png

You can view all the changes made to a stream or project, including the following details:

  • The stream version created by the new changeset.
  • The date and time the stream version was created.
  • The name of the user who made the delivery, the type of delivery, and any comment entered by the user at the time of delivery.

For details about viewing changesets, see the following topics:

Web client View and compare changesets
Desktop client View and compare changesets

Each item in a changeset includes the following details:

  • The type of change, for example, Modification.
  • The repository path of the file or folder.
  • The item revision.
  • Any related change requests.

Back to top

Changeset health

Changeset health is displayed visually as a combination of the plugin opinions of the changes and the review state.

The following labels indicate the changeset state.

Label Description
The changeset is healthy, and the review was successful.
The changeset is not healthy, or the review failed.
The changeset is unstable.
Plugins are running on the changeset.
Plugins are scheduled to run on the changeset.
No plugins were run on the changeset, and no review is available.
The changeset was stopped.

See also: