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. |
...