Trigger pipeline action

One application may consist of several services. The most common is the division into frontend and backend. Usually, each service is served from a separate repository, which means they occupy two different projects.

Thanks to this action, you can, for example, you can use it to release the frontend of the application once the backend has been successfully deployed:

Pipeline example

Adding 'Trigger pipeline' action

When adding the action you need to specify:

1. The pipeline to be triggered
2. The comment that will be added to the newly executed pipeline

3. The revision with which the pipeline will be run. You can choose:

   • The HEAD revision of the branch to which the second pipeline is assigned
   • The same revision that was used to trigger the parent execution. This is especially useful if both pipelines operate within one repository
   • A specific revision

4. Whether the parent pipeline should wait until the triggered pipeline finishes, or run it without waiting for the results.

Setting a trigger condition

Passing parameters

It is possible to send parameters to the triggered pipeline. The option is available in the Variables tab: Adding variables

For example, if the parent pipeline is triggered when a new tag is pushed to the backend repository, you can pass the value of that tag to the second pipeline in the frontend project: Adding variables