A snapshot is a collection of build versions (project versions) for the release's projects which are sent through the pipeline. As a release progresses, newer versions of projects are assembled to create new snapshots. A release may consist of dozens, or even hundreds or thousands, of snapshots over its lifetime, depending on the release's size and duration. There are several ways in which snapshots can be created.
- By a release manager by explicitly identifying the versions of the projects/packages in the release. See Creating a Snapshot.
- By associating a project/package build to the release. As such, once the build completes, the new project version is overlaid on top of the most recent release snapshot to produce a new snapshot.
- By promoting an existing build to a release. In this case, a new snapshot is created with the selected project version overlaid.
- Using a Continuous Integration trigger (Webhook, Poll SCM, or Scheduled Build Trigger) to automatically associate the new build with the release.
- Using the REST API to submit a build request, and associate it to the release.
| Tip |
|---|
All snapshots which reach Completed status are sent to the pipeline for execution, and marked Initiated. Only one snapshot per release can be created (Pending) at a time. However, many snapshots can be executing the pipeline for the same release in parallel. |
...
Column | Description | ||
|---|---|---|---|
Project Name | The name of the project within the snapshot. | ||
| Project Version | The version of the project build within the snapshot. | ||
| Package Name | The package name for the project build within the snapshot. Only applies to partial deployment projects. If All Files is being used, you will see (All Files) for package name. | ||
| Stream | The stream from which the package is project version was built. | ||
| Request All Files | Whether or not the package contains all the files for the project. Only applies to partial deployment projects. | ||
Status | The status of the individual project version within the snapshot. @since 5.3.0.2, Statuses are:
| ||
| Error Message | The error message of the failed build, if the status is Failed. | ||
Built On | The date and time when build was executed. @since 5.3.0.2 | ||
| Built By | The user who initiated build. @since 5.3.0.2
|
...
| Column | Description | ||
|---|---|---|---|
| Project Name | The name of the project within the snapshot. | ||
| Project Version | The version of the project build within the snapshot. | ||
| Package Name | The package name for the project build within the snapshot. Only applies to partial deployment projects. If All Files is being used, you will see (All Files) for package name. | ||
| Stream | The stream from which the package is project version was built. | ||
| File Type | The object type of the file if applicable. | ||
File Name (with Path) | The path and name for the specific file. | ||
| Sequence | The sequence number of the file within the package if applicable. | ||
| Revision | The latest SCM revision for the file or project. | ||
| Committed By | The committer username for the SCM revision. | ||
| Commit Message | The commit message for the SCM revision. | ||
| Built On | The date and time when build was executed. | ||
| Built By | The user who initiated build.
|
...