---
name: devsecops-devsecops-triggers
title: Triggers
description: DevSecOps continuous integration and continuous deployment pipelines provide a set of default triggers.
last-updated: 2025-07-22
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/devsecops?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Triggers
{: #cd-devsecops-triggers}

DevSecOps continuous integration and continuous deployment pipelines provide a set of default triggers.
{: shortdesc}

|Pipeline |Name	|Description |State |
|:----------|:------------------------------|:------------------|:----------|
|Pull request		|Git PR Trigger		|Runs the pull request pipeline on pull requests within the Application Repository.			|Enabled			|
|Pull request 		|Manual Trigger 		|Runs the pull request pipeline on a specified commit or branch, on demand.			|Enabled			|
|Promotion 		|Git Promotion Validation Trigger 		|Runs the promotion validation pipeline when a pull request is opened/updated on the `target-environment` branch of the Inventory.	|Disabled			|
|Continuous integration		|Git CI Timed Trigger		|Runs the continuous integration pipeline on the `master` branch of the Application Repository every day at 4 AM. |Disabled			|
|Continuous integration		|Git CI Trigger		|Runs the continuous integration pipeline when a commit is pushed to the master branch of the Application Repository.	|Enabled			|
|Continuous integration		|Manual Trigger 		|Runs the continuous integration pipeline on a specified commit or branch, on demand.		|Enabled			|
|continuous deployment		|Git CD Timed Trigger		|Runs the continuous deployment pipeline every day at 4 AM.	|Disabled			|
|continuous deployment		|Git CD Trigger		|Runs the continuous deployment pipeline when a commit is pushed to the `target-environment` branch of the Inventory.	|Disabled			|
|continuous deployment		|Manual CD Trigger		|Runs the continuous deployment pipeline on the `target-environment` branch of the Inventory, on demand.	|Enabled			|
|continuous deployment		|Manual Promotion Trigger		|Runs the promotion pipeline to promote inventory changes from the `source-environment` branch to the `target-environment` branch.	|Enabled			|
|Continuous compliance		|Git CC Timed Trigger		|Runs the continuous compliance pipeline every day at 4 AM.	|Enabled			|
|Continuous compliance		|Manual CC Trigger		|Runs the continuous compliance pipeline on the `environment-tag` tag of the Inventory, on demand.	|Enabled			|
|Continuous integration, continuous deployment, continuous compliance		|Evidence Pruner Timed Trigger		|Runs the pipeline every day at 2AM to clean up all the old evidence generated before `evidence-retention-days` days.	|Disabled by default.			|
|Continuous integration, continuous deployment, continuous compliance		|Evidence Pruner Manual Trigger 	|Runs the pipeline to clean up all the old evidence generated before `evidence-retention-days` days. Runs on demand.	|Enabled			|
{: caption="Triggers" caption-side="top"}

You can [add triggers](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-add-pipeline-triggers&format=markdown) to the set of default triggers.
{: tip}

## Triggering a Pipeline Using CLI or API
{: #triggering-cli-api}

- In addition to default triggers, you can manually start pipeline runs using the IBM Cloud CLI or a REST API call.
   - CLI: Use the IBM Cloud CLI to trigger a pipeline by specifying the toolchain and pipeline IDs.
   - API: Send a POST request to the pipeline trigger endpoint with the appropriate authorization headers and payload.
For step-by-step instructions and usage examples, see [Using Triggers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelines&interface=api&format=markdown#using-triggers).