SSWConsulting / SSWConsulting/SSW.Rules
Build - Long pipeline queues slowing down deployment
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
cc: @JackLeerson @adamcogan @jasontaylordev @pierssinclairssw
To @bradystroud,
When lots of PR's on the SSW.Rules.Content repository are merged at once, a build pipeline starts for each merge. As the pipeline can only run one build at a time (~25min each) it creates a long queue of builds meaning changes can take hours to be deployed.
To get changes out faster, I have been manaully cancelling unnecessary builds
Figure: Red striped lines are manually cancelled builds
- Optimise pipelines to ensure long queues are not created
-Brady
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the build pipeline used for the SSW.Rules.Content repository and review how concurrent merges create queued builds. Confirm the current single-build limit and define completion as preventing unnecessary queued builds while keeping required changes deployable faster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100