Versions Compared

Old Version 6

changes.mady.by.user Karl Henselin

Saved on

compared with

New Version 7

changes.mady.by.user Blake Westmoreland

Saved on

Key

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

A Snapshot is a collection of build versions (project versions) of release 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, hundreds or even 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 Project Triggers 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 Completedstatus 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

The name of the project within the snapshot.

Package

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.

Status

The status of the individual project version within the snapshot. Statuses are:

(blue star) Pending - The project is has not yet been 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.

(blue star) Failed - The project has failed to build.

(blue star) Aborted - The build execution was aborted by the user or the snapshot version was aborted by the user while aborting the snapshot. The In the case where it is aborted because the snapshot was aborted, the build execution will still be running and could be promoted to the release later.

(blue star) Submitted - The project is currently being built for the snapshot.

(blue star) Completed - The project has been built successfully for the snapshot. This will be seen only if build was submitted during create snapshot process.

(blue star) Existing - There were either no changes detected or user had selected a previous version to use in the snapshot.

Note

Once the all project versions in the snapshot are completed 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.

Version

The version of the project build within the snapshot.

Branch

The Branch from which the project version was built.

Request Error

The error message of the failed build, if the status is (blue star) Failed.

Built On

The date and time when build was executed.

Built By

The user who initiated build.

Note

The user will be a system user if 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)

...