Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CDS-40448-run-stages-in-parallel #802

Merged
merged 6 commits into from
Mar 8, 2023
Merged

CDS-40448-run-stages-in-parallel #802

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
9dc5cd0
CDS-40448-run-parallel-stages
roshnisarangadharan Feb 23, 2023
86b8061
CDS-40448-run-multiple-stages
roshnisarangadharan Feb 23, 2023
7d9f338
CDS-40448
roshnisarangadharan Feb 24, 2023
33aad7e
Update run-stages-in-parallel.md
roshnisarangadharan Mar 1, 2023
667a6f9
Apply suggestions from code review
roshnisarangadharan Mar 8, 2023
2453c96
Update docs/platform/8_Pipelines/run-stages-in-parallel.md
roshnisarangadharan Mar 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update docs/platform/8_Pipelines/run-stages-in-parallel.md 
Co-authored-by: Michael Cretzman <58786311+michaelcretzman@users.noreply.github.com>
  • Loading branch information
@roshnisarangadharan @michaelcretzman
roshnisarangadharan and michaelcretzman authored Mar 8, 2023
commit 2453c965d758eb8166d233dfa10b6b96112e2d27
2 changes: 1 addition & 1 deletion docs/platform/8_Pipelines/run-stages-in-parallel.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Navigate between the stages by hovering over them and selecting the stage.

![](./static/run-stages-in-parallel.png)

A [Resource Constraint](../../continuous-delivery/cd-deployments-category/deployment-resource-constraints.md) step is added to every stage automatically to make sure that two infrastructures are not being deployed concurrently. Hence, one of the two parallel stages will deploy first. Once the deployment of the winning stage finishes, the other stages will start.
A [resource constraint](../../continuous-delivery/cd-deployments-category/deployment-resource-constraints.md) step is added to every stage automatically to make sure that you are not using two infrastructures simultaneously. Hence, one parallel stage executes first. Once the execution of the first stage finishes, the other stage(s) will start.

You can deploy multiple services to multiple environments in a single stage (for more information, go to [Use multiple services and environments in a deployment](https://developer.harness.io/docs/continuous-delivery/cd-deployments-category/multiserv-multienv/)). However, running multi-service stages in parallel will deploy each service to each environment in parallel. This can become very complicated. For such use cases, we recommend using multiple stages.