feat: publish charm detect all charm artefacts - #963
Conversation
cbartz
left a comment
There was a problem hiding this comment.
LGTM, but one question regarding multi-charm support
Test results for commit 5498038Test coverage for 5498038 Static code analysis report |
Test results for commit 5498038Test coverage for 5498038 Static code analysis report |
Test results for commit 5498038Test coverage for 5498038 Static code analysis report |
Test results for commit 5498038Test coverage for 5498038 Static code analysis report |
Test results for commit 5498038Test coverage for 5498038 Static code analysis report |
Test results for commit 5498038Test coverage for 5498038 Static code analysis report |
Unused entries in .trivyignoreImage: ghcr.io/canonical/test-foo:73ebae26eaf71e0462669ed86b00b03f1351934e-_1.0_amd64 The following CVEs are in |
1 similar comment
Unused entries in .trivyignoreImage: ghcr.io/canonical/test-foo:73ebae26eaf71e0462669ed86b00b03f1351934e-_1.0_amd64 The following CVEs are in |
Unused entries in .trivyignoreImage: ghcr.io/canonical/test:a8ba9319ad0fe10278b87cf705838818e280ccdd-_1.0_amd64 The following CVEs are in |
* feat: merged plan & publish multiple charms * ci: test workflow * docs: changelog * ci: distribute build * ci: revert back to main * ci: rebuild dist
Applicable spec:
Working run proof
https://github.com/canonical/jenkins-agent-operator/actions/runs/22840905575/job/66248356984?pr=139 (PR: canonical/jenkins-agent-operator#139)
Overview
Rationale
Workflow Changes
Checklist
urgent,trivial,complex)