Status | The current status of the release. Started - the release is eligible to process snapshots Paused - the release has been paused, and is not currently eligible to process snapshots Completed - the release has ended, and will never process snapshots again (status can still be reverted back to started if needed)
Since FlexDeploy 8.0, all new Releases will be in Started status and Not Started status has been removed. This means that Release may be Started even without any content, and obviously Snapshot can only be created after some content is added to Release. |
Snapshot Schedule | A cron expression to initiate the creation of a snapshot on a regular basis, using new project versions for all release projects. When Snapshot Schedule is added or updated, Project-level scheduled build or webhook triggers are created, which can be viewed from the project triggers screen as well. More than one cron expression can be provided using ; as a separator. This would allow for more complex schedules, but all projects/packages in the release will use the same schedule. For example, When a release is Completed or Paused, all the scheduled build triggers for each project/package in the release will be deleted. | Info |
|---|
Release Scheduled Build Processing | | Info |
|---|
Release Scheduled Build Processing |
When a release is Completed or Paused, all the scheduled build triggers for each project/package in the release will be deleted. All projects/packages in a release with a build environment Build Environment set will be configured for build trigger based on the snapshot schedule. This will initiate a build for each release project by creating a snapshot for the release containing all new project versions. . If project is Webhook enabled then Webhook trigger is created otherwise Scheduled Build trigger is created. For Scheduled Build trigger, build will be initiated for each release project/package on Snapshot Schedule, and for Webhook trigger build will run via Incoming Webhook. New snapshot will be created automatically on schedule, if changes are found for Scheduled Build projects or new builds are found for project/package. This means that for Webhook enabled projects, incoming webhook should initiate build. You can view (but not edit) associated
scheduled build A single release snapshot is created even when more than one project/package is found to have changed in SCM or built via Webhook. Projects with SCM set to None Change detection is not possible. If there is a newer version for the project than what is in the latest snapshot, the new snapshot will contain this newer version. Build is never invoked automatically based on the snapshot schedule in this case as SCM is None, but separate build triggers can be created from the project to automate this.
Projects with SCM other than Noneand Webhook Disabled Change detection will be performed on Snapshot Schedule. If changes are detected in SCM, a new build will be initiated for those projects as part of the snapshot creation. If no changes are found in SCM, then the latest version for that project, branch, and package combination will be used in the snapshot.
Projects with SCM and Webhooks are Enabled Change detection is not performed on Snapshot Schedule. Incoming Webhook is responsible for performing build based on incoming payload. New build for project/package will be picked up on Snapshot Schedule. Incoming Webhook scripts will only find project/package to build if Webhook is Enabled on Project and project/package is added to Release with Build Environment.
If there are no changes found in any projects/packages and no newer project versions since the latest snapshot, then a snapshot will not be created. A project or package can be added to multiple releases with the same branch. In such situations, if the project/package is built once, even without release selection, that latest project version will be included in all releases that contain that project/package with the selected build branch, when individual snapshot schedule trigger fires for those releases.
|
|
