StackStorm / StackStorm/st2-packages
Package revision race
Open
Nobody has claimed this yet.
bug
- Dominant language
- Shell
- Stars
- 28
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
Between fetching a revision number as a part of checkout and uploading a new package with this revision during deploy, every parallel package build will end up with the same revision number and will fail on deploy stage due to package already being present.
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 with .circle/buildenv_st2.sh line 46 and circle.yml lines 44 and 87, tracing how parallel package builds obtain and upload revisions. Inspect the parallel-build path; done means concurrent builds receive non-colliding revisions and deploy without the existing-package failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100