StackStorm / StackStorm/st2-packages
Failure during package upload result in revision desync
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 28
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
If the package for one of the flavors could not be uploaded during deploy stage, it would be considered a build failure yet the packages that were uploaded during the same build would not be deleted either. This creates desynchronization between revision numbers of packages across different flavors, which in turn leads to the confusion when you're trying to match packages between each other or with the build they were created in.
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 tracing the automated deploy-stage package upload flow and its failure handling across flavors. Done means a failed upload does not leave packages from the same build behind, so package revisions remain synchronized and can be matched to one another and their build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system, ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100