Versions Compared

Old Version 65

changes.mady.by.user Emily Simon

Saved on

compared with

New Version 66

changes.mady.by.user Chandresh Patel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

To view the details of the projects in the snapshot, click on the link in the Snapshot Name column.

Image RemovedImage Added

Column

Description

Project Name

The name of the project within the snapshot.
Project VersionThe version of the project build within the snapshot.
Package NameThe 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.
Request All FilesWhether 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.  Status . @since 5.3.0.2, Statuses are:

  • Pending - the project is has not yet been built processed for the snapshot. There may be number of different outcomes for project, i.e. may be built or just new version may be used.
  • Failed - the project has failed to build.
  • Build Submitted - the project is currently being built for the snapshot.
  • New Build Completed - the project has been built successfully for the snapshot.
  • Failed - the project has failed to build.
  • Existing - the snapshot is utilizing an already built version of the projectThis will be seen only if build was submitted during create snapshot process.
  • No Previous Version - the project was not present in previous snapshot, so it is newly added to snapshot.
  • No Change - project version is same as previous snapshot.
  • Newer Version - project version is newer than previous snapshot. Project was built manually, triggers, rest call or using incoming webhook.
  • Older Version - project version is older in comparison to previous snapshot. User must have selected older version for backout purposes during create snapshot process.
Note

Once the all project versions in the snapshot are Completed or Existingcompleted successfully, the snapshot will be Completed, and then sent for pipeline execution (Initiated). If any project versions fails to build, snapshot will be marked as Failed and will not be executed through pipeline.


Error MessageThe error message of the failed build, if the status is Failed.

Created Built On

The date and time in which the snapshot was created.Created when build was executed. @since 5.3.0.2
Built By

The user who created the snapshot.initiated build. @since 5.3.0.2

Note

The user will be a system user if the snapshot was created via a project build associated to the release, as multiple user may have contributed to it.build was initiated by automated process. For example,

  • webhook - If build was triggered by incoming webhooks.
  • buildsubmitmonitor - if build was triggered during create snapshot (initiated by user or release schedule)