Synchronize Workflows in your Pipeline Using Barriers
Barriers allow you to synchronize different Workflows in your Pipeline, and control the flow of your deployment systematically.
In this topic:
Before You Begin
Review: Barriers and Synchronization
When deploying interdependent services, such as microservices or a large and complicated application, there might be a need to coordinate the timing of the different components' deployments. A common example is the need to verify a group of services only after all the services are deployed successfully.
Harness Workflows address this scenario using barriers. Barriers allow you to synchronize different Workflows in your Pipeline, and control the flow of your deployment systematically.
Barriers have an effect only when two or more Workflows use the same barrier name, and are executed in parallel in a Pipeline. When executed in parallel, both Workflows will cross the barrier at the same time.
If a Workflow fails before reaching its barrier point, the Workflow signals the other Workflows that have the same barrier, and the other Workflows will react as if they failed as well. At that point, each Workflow will act according to its Failure Strategy.
Step: Configure Barrier
To use a barrier, do the following:
- In your Workflow, click Add Step.
- Click Barrier. The Configure Barrier settings appear.
- In Identifier, enter a name for the barrier. This name must be identical to all the other related barriers in the other Workflows you want to impact.
- In Timeout, enter the timeout period, in milliseconds. For example, 600000 milliseconds is 10 minutes. The timeout period determines how long each Workflow with a barrier must wait for the other Workflows to reach their barrier point. When the timeouts expire, it is considered a deployment failure.
- You can have multiple barriers in a Workflow. Every Barrier in the same Workflow must use a unique Identifier.
- Ensure the identifier string for each related barrier across the different Workflows matches.