Skip to content

fix(ci): release-test-tools Dockerfile path (drop subtree prefix)#120

Merged
ycpss91255 merged 1 commit into
mainfrom
fix/release-test-tools-path
Apr 24, 2026
Merged

fix(ci): release-test-tools Dockerfile path (drop subtree prefix)#120
ycpss91255 merged 1 commit into
mainfrom
fix/release-test-tools-path

Conversation

@ycpss91255
Copy link
Copy Markdown
Contributor

Summary

Bootstrap workflow_dispatch of release-test-tools.yaml failed:

ERROR: failed to build: resolve : lstat template: no such file or directory

release-test-tools.yaml runs in the template repo, so Dockerfile.test-tools is at dockerfile/Dockerfile.test-tools — not template/dockerfile/Dockerfile.test-tools (that's the subtree path downstream consumers see, used by build-worker.yaml which executes in a downstream's checkout).

Changes

  • .github/workflows/release-test-tools.yaml: template/dockerfile/dockerfile/ + comment explaining the path asymmetry.
  • test/unit/template_spec.bats: regression test asserting the template-repo-local path and no subtree prefix leak.
  • TEST.md: 663 → 664.

Test plan

  • make -f Makefile.ci test local — 664/664 pass
  • CI template self-test green
  • Post-merge: re-trigger release-test-tools.yaml via workflow_dispatch → pushes ghcr.io/ycpss91255-docker/test-tools:latest successfully

release-test-tools.yaml runs in the template repo itself, not in a
downstream consumer, so the Dockerfile lives at dockerfile/... — the
template/dockerfile/... path I wrote is what build-worker.yaml sees
(that one executes in the downstream's checkout, where template/ is
the subtree root). Bootstrap workflow_dispatch run failed with
`lstat template: no such file or directory`.

Added regression test asserting the path is template-repo-local and
no subtree-prefixed path leaks back in.
@ycpss91255 ycpss91255 merged commit 6bb8a5e into main Apr 24, 2026
3 checks passed
@ycpss91255 ycpss91255 deleted the fix/release-test-tools-path branch April 24, 2026 06:32
This was referenced Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant