CLI Release Pipeline: manual approval for promotion from `test` to `release`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Add a method for promoting the artifacts from the test to the release step in the CLI Release Pipelines.
Currently, the full test suite fails with a few of the 90 tests failing, blocking the pipeline and leading to out-of-band promotions. We should add a mechanism which allows us to quickly and easily review the results of the test step and promote to release in-pipeline rather than do an out-of-band execution of the release step. This will make things easier to review, document, and involve less opportunity for human error.
https://docs.aws.amazon.com/codepipeline/latest/userguide/approvals-action-add.html
Contributor guide
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
The issue names the CLI Release Pipelines and links AWS CodePipeline approval-action documentation; start by locating the pipeline definition and reviewing that approval action. Done means test results can be reviewed and promotion from test to release can be approved in the pipeline without an out-of-band release execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- ci-cd, cli, cloud, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100