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

Troubleshooting concurrency groups #2503

Merged
merged 6 commits into from
May 16, 2024
Merged

Troubleshooting concurrency groups #2503

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
2a592a3
Troubleshooting concurrency groups
pzeballos Sep 28, 2023
82d3b7c
Update pages/pipelines/controlling_concurrency.md
gilesgas May 16, 2024
9d19096
Merge remote-tracking branch 'origin/main' into concurrency-group-help
gilesgas May 16, 2024
4bd035c
Merge remote-tracking branch 'origin/main' into concurrency-group-help
gilesgas May 16, 2024
489ba80
Minor clarification
gilesgas May 16, 2024
0f715a0
Minor formatting tweak
gilesgas May 16, 2024
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
6 changes: 4 additions & 2 deletions pages/pipelines/controlling_concurrency.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,10 @@ For example, if you have two pipelines that each deploy to a different target bu

Concurrency groups guarantee that jobs will be run in the order that they were created in. Jobs inherit the creation time of their parent. Parents of jobs can be either a build or a pipeline upload job. As pipeline uploads add more jobs to the build after it has started, the jobs that they add will inherit the creation time of the pipeline upload rather than the build.

> 🚧 `concurrency_group` and `block` / `input` steps
> Note that both [block](/docs/pipelines/block-step) and [input](/docs/pipelines/input-step) steps cause the steps to be uploaded and scheduled at the same time, which breaks concurrency groups. These two steps block jobs being added to the concurrency group, but do not affect the jobs' ordering once unblocked. The concurrency group won't be added to the queue until the `block` or `input` step is unblocked, and once it is, the timestamp will be from the pipeline upload step.
> 🚧 Troubleshooting and using `concurrency_group` with `block` / `input` steps
> When a build is blocked by a concurrency group, you can check which jobs are in the queue and their state using the [`getConcurrency` GraphQL query](/docs/apis/graphql/cookbooks/jobs#get-all-jobs-in-a-particular-concurrency-group).
> <p>
> Be aware that both the [`block`](/docs/pipelines/block-step) and [`input`](/docs/pipelines/input-step) steps cause these steps to be uploaded and scheduled at the same time, which breaks concurrency groups. These two steps block jobs being added to the concurrency group, but do not affect the jobs' ordering once unblocked. The concurrency group won't be added to the queue until the `block` or `input` step is unblocked, and once it is, the timestamp will be from the pipeline upload step.

## Concurrency and parallelism

Expand Down
Loading