(pipelines): limit assets concurrency
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Description
There are limits to how many CodeBuild projects can run in parallel (it's either 5 or 20), and asset publishing is liable to hit those.
Rather than queueing builds, any builds over the limit are just outright failed.
The CodePipeline generator should take this into account when generating asset publishing stages.
### Use Case
Hitting CodeBuild limit.
### Proposed Solution
Property to limit asset concurrency.
### Other information
_No response_
### Acknowledge
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
Contributor guide
Research direction
Start by locating the CodePipeline generator and its asset publishing stage logic, then review how CodeBuild projects are generated and whether existing properties control parallel work. Done means the generator accepts an asset-concurrency limit and avoids scheduling more builds than the configured CodeBuild limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100