website logo
Sign Up PricingApp Templates
⌘K
🚀Getting started
Create an account in Microtica
Create an application from template
Import an existing application
Scaling Applications in Microtica
Assign a Custom Domain
⏰Changelog
📚Ready-to-use Templates
Strapi Serverless
Medusa Server
Appwrite
SPA on CloudFront
Amazon EKS
Node.js
n8n Workflow Automation
Next.js
🤖Migrate to Microtica
Migrate from Heroku to AWS
🚦Pipelines
Pipeline Syntax
Steps
Stages
Artifacts
Variables
🔗Integrations
Connect an AWS account
Connect an Existing Kubernetes Cluster
Connect a Container Registry
⚙️Project Settings
Manage teammates
Manage pricing plan and billing
Docs powered by archbee 
4min

Trigger Pipeline

Initiate execution of a pipeline from another pipeline.

This step is useful for splitting the automation process in two or more pipelines for better management and reusability of automation.

This step will initiate the pipeline execution and will not wait for pipeline to finish. Pipeline execution will continue running asynchronously.

Syntax

microtica.yaml
|


Parameter

Description

Required

title

The display name of the step.

No

type

The type of the Microtica built-in step. Should always be trigger-pipeline for this type of step.

Yes

pipeline

The ID of an existing pipeline to be triggered.

Yes

branch_filter

Initiate pipeline execution only for commit/manual trigger on specified branch. If not specified, pipeline will be triggered on every pipeline execution. E.g. develop, feature/upgrade-eks etc.

No

ref

Branch or tag ref the triggered pipeline should pull the code from. Default: refs/heads/master

No

Trigger pipeline when commits are made on specific branch

Microtica allows you to trigger another pipeline only if the parent pipeline was trigged from a specific branch or tag.

This is very useful for use-cases when you want to split pipeline logic in two or more pipelines. For example, you can have one pipeline that runs the build, test and packaging and triggers another pipeline that deploys the code on specific environment (dev, test, prod) based on branch the parent pipeline was triggered from.

microtica.yaml
|


Given the above configuration, the pipeline will trigger another pipeline with ID 2efeaf06-7d87-4092-ba66-94877c6f2d47 only if the parent pipeline was triggered from branch develop.

By setting the ref value to develop branch we tell the pipeline to pull the code from develop branch.

Updated 03 Mar 2023
Did this page help you?
Yes
No
UP NEXT
CloudFormation Component
Docs powered by archbee 
TABLE OF CONTENTS
Syntax
Trigger pipeline when commits are made on specific branch