Matrix testing images and recommendations with or without base images
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 141
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
What is the best / recommended approach with recommendations and matrix testing when some images might not have base images which results into image has no base image exit and non-zero exit code?
Currently I've split cves and recommendations to own steps as follows:
- name: Image CVEs
uses: docker/scout-action@f8c776824083494ab0d56b8105ba2ca85c86e4de # v1.18.2
with:
command: cves
image: ${{ vars.IMAGE }}
only-severities: ${{ inputs.severities || 'critical,high' }}
only-fixed: true
summary: true
format: json
exit-code: true
- name: Image recommendations
uses: docker/scout-action@f8c776824083494ab0d56b8105ba2ca85c86e4de # v1.18.2
continue-on-error: true
with:
command: recommendations
image: ${{ vars.IMAGE }}
only-severities: ${{ inputs.severities || 'critical,high' }}
only-fixed: true
summary: true
format: json
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 reviewing the provided GitHub Actions workflow and the docker/scout-action cves and recommendations commands, focusing on how images without base images affect exit codes. Define the desired behavior for matrix entries with and without base images, then verify it across both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, javascript
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100