Running multiple commands causes failure in the middle and rest of the commands is not executed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 141
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
The order of the commands matter, if cve command is in the middle, the rest of the commands will not be executed in case of failure.
In the first example , only the first 2 commands are executed, the error stops it.
id: docker-scout-scan
uses: docker/scout-action@v1
with:
command: quickview,cves,sbom,recommendations
exit-code: true
In the second example the behaviour is correct and all comands run
id: docker-scout-scan
uses: docker/scout-action@v1
with:
command: quickview,sbom,recommendations,cves
exit-code: true
This is somehow not transparent or obvious to the users.
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
Start by reproducing the docker/scout-action@v1 workflow with command set to quickview,cves,sbom,recommendations and then quickview,sbom,recommendations,cves, comparing the command execution after a failing cves step. Trace the action's command handling and make the behavior consistent or clearly communicated when exit-code is true; done means the remaining commands behave as intended in both orderings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, javascript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100