> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/~/changes/7YIrhOgqbpKF1lkWsq0G/guides/deploying-workloads/triggers-for-ci-cd.md).

# Triggers for CI/CD

### 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](/ozone-end-user-guide/~/changes/7YIrhOgqbpKF1lkWsq0G/guides/quickstart/setting-up-ecosystem-integrations.md)
* 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