test: empty commit to validate buildx cache behavior#105
Draft
ashiramin wants to merge 1 commit into
Draft
Conversation
Empty commit on top of main (commit 1fe409d). No file changes — testing whether an empty PR's build will pick up fresh Debian packages or reuse the stale buildx layer cache. Today's :main trivy scan flagged 11 packages (libcap2, libsystemd0, libudev1, openssh-client, jq/libjq1, python3.13-*). If this PR's trivy-pr scan reports the same set, the hypothesis is confirmed: empty commits do not bust the buildx cache and the failure persists. If trivy-pr passes, something else is invalidating the cache and the analysis was wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Empty commit experiment to falsify (or confirm) the claim that an empty PR's
buildjob reuses the stale buildx layer cache and therefore can't fix the:maintrivy scan.Setup: branched from
main(commit 1fe409d), one empty commit, no file changes.Expected outcome (per the analysis in PR #104):
buildjob: succeeds (cache hit, fast build, image identical to current:main)trivy-prjob: fails with the same 11 packages flagged by today's failing:mainscan (libcap2, libsystemd0, libudev1, openssh-client, jq/libjq1, python3.13-*)Alternative outcome (analysis is wrong):
trivy-prpasses → something else is invalidating the cache → revisit PR Add refresh button to docker.yml so trivy scan failures are recoverable without pinning #104.Will close this once the result is observed either way.
🤖 Generated with Claude Code