Performing a Release

How to perform releases and gather information about a particular release

Releases are mutations that propagates to an environment. In this Section, you will learn how to perform and monitor a release that makes a change to the environment.

Facets is built on a key principle that any changes (release) to an environment has to happen through a single mechanism. These changes could be of

  1. New code or updates (new builds)
  2. New resources or updates
  3. New interactions, schema, policies or updates

Release Schedule

Releases are of two types

  1. Scheduled Release: A Scheduled release pattern is defined in the "edit" environment section in the "Misc" tab. For e.g., a 30 5 * * * would mean a scheduled release (full) will happen at 5:30 AM, every day.

  2. On-demand Release: An on-demand release can be performed in an environment from the "Releases" page. You can make a full or partial release from this page.

    1. Release - Perform a full release i.e. every resource on the Blueprint and their qualified builds will sync to the environment
    2. Selective - Perform a selective release of one or selected resources. This is usually used as a hotfix to the environment

Release Candidates

Once a release is performed the following details are available for it.

StartedWhen was the release triggered
Last CommitThe git commit up to which the IDP has pulled the changes
Release TypeRELEASE (Indicates a full release)
LAUNCH (Environment launch)
HOTFIX (Indicates a selective release)
Triggered ByEither a user
Facets Bot (indicating a scheduled release)
Action1. Release Details
2. Terraform Logs

Release Details

The release details Action shows the resource changes i.e Creations, Modification (i.e. new versions of apps) or Destruction.


Release Details

Release Logs

The release logs provide a detail view of the generated terraform logs.


Terraform Logs

Release Summary

The release summary page is aggregated release summary for last 30 days. This provides metrics that can lead to improvement in the SDLC.

Successful ReleasesNumber of Successful Releases in last 30 days
Failed ReleasesNumber of Failed Releases in last 30 days
Deployment FrequencyAverage deployment per day
Change Failure RatePercentage of changes that resulted in a failure