User Guide
Search…
Release workflows with Gated Approvals
Use Ozone's Releases for combining pipelines and approvals as release stages

Pre-requisites

  • Setup a JIRA or Slack integration for approvals from the ecosystem integrations
  • Link a pipeline (or many more) to your application
  • You must have setup a custom application for CI/CD

Setting up Application Releases

  • Navigate to the application in context (Application -> Select Application)
  • Navigate to Releases
  • Click on +CREATE
  • Add the approval and pipeline steps as needed to execute serially
  • You are now ready to execute this Application's Releases
Ozone supports three kinds of release execution triggers
  • Release runs triggered from Ozone's UI
  • Release runs that are scheduled by the user
  • Release runs that are triggered by external systems and events

Triggering a Release from Ozone's UI

  • Navigate to the application in context (Application -> Select Application)
  • Navigate to Releases
  • Click on "RUN" for the release you would like to execute
  • Release executions are visible under the Application -> Selected Application -> Release Runs
  • You are now ready to execute this Application's Releases

Triggering a Release from Ozone's Schedules

  • Navigate to the application in context (Application -> Select Application)
  • Navigate to Schedules
  • Click on "ADD" for the release you would like to schedule
  • Enter the schedule name and timing
  • Map it to a Release by applying this schedule to a Release workflow
  • Click on "SCHEDULE" to enforce the pipeline to run in a scheduled fashion
  • Release runs are now visible under the Application -> Release Runs section
  • Click on a Release run to view it's current status and logs

Triggering a Release from external systems

In addition to on-demand and scheduled release executions, Ozone offers you a templated way to trigger release (and pipelines) by listening to events on an external system. Ozone supports the following platforms natively:
Supported External Systems:
  • Bitbucket
    • Supports triggers from Branch Pushes and Pull Requests
  • Github
    • Supports triggers from Branch Pushes and Pull Requests
  • Gitlab
    • Supports triggers from Branch Pushes and Pull Requests
  • Generic
    • Trigger from any external system that is not supported by Ozone (for example, Postman)

Setting Up External Triggers

  • Integrate the supported providers (Github, Gitlab and Bitbucket) from the ecosystem integrations
  • Navigate to the Webhooks section (Deployment Config -> Webhooks)
  • Select the external system to respond to
  • Select the repositories and events to watch
  • Select the application that it maps to on Ozone
  • Select the Releases that need to be executed on this webhook being triggered
  • The Release executes when the external system triggers it based on the webhook setup
  • Release runs are visible under the Application -> Release Runs section when the triggers get executed
  • Click on a Release run to view it's current status and logs
Copy link
Outline
Pre-requisites
Setting up Application Releases
Triggering a Release from Ozone's UI
Triggering a Release from Ozone's Schedules
Triggering a Release from external systems