Skip to content

DO NOT MERGE: verify build-docker.yml PR trigger - #21978

Closed
kadykov wants to merge 5 commits into
darktable-org:masterfrom
kadykov:test/verify-build-docker-pr-trigger
Closed

DO NOT MERGE: verify build-docker.yml PR trigger#21978
kadykov wants to merge 5 commits into
darktable-org:masterfrom
kadykov:test/verify-build-docker-pr-trigger

Conversation

@kadykov

@kadykov kadykov commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Test PR — verify build-docker.yml on pull requests

This is a test-only draft PR. The only change is a non-functional comment line added to Dockerfile to trigger build-docker.yml's new pull_request path filter.

Expected behaviour:

  • Build, test and push CI Docker image job runs
  • All four Linux CI matrix configurations build and pass
  • The "Tag and push" step is skipped (if: github.event_name != 'pull_request'), so GHCR is not modified

This verifies the CI refactoring in #21972. Results will be linked in that PR thread.

Do not merge — will be closed once the run is confirmed.

- Remove .ci/Dockerfile (2016-era Jenkins artefact, superseded)
- .devcontainer/devcontainer.json: switch to pre-built GHCR image
- .github/workflows/build-docker.yml: implement build→test→push workflow
  that builds from .devcontainer/Dockerfile, runs all Linux CI matrix
  configurations via .github/scripts/test-image.sh, and only pushes to
  GHCR if every build succeeds
- .github/workflows/ci.yml: Linux jobs pull ghcr.io/darktable-org/
  darktable-build:latest; permissions scoped to contents:read only
- .github/scripts/test-image.sh: new helper script that runs all four
  Linux CI matrix configurations (GNU16 Release, LLVM22 Release,
  GNU16 Debug, GNU16 Release+tests) against a candidate Docker image;
  also callable locally for manual validation
- .devcontainer/README.md: update CI environment section to describe
  the build→test→push workflow and correct the GHCR image update cadence
- .gitignore: add install/ (created by test-image.sh during local runs)
…docker-build workflow, authenticate in GHCR for pulling images in CI workflow
…patch

Add a pull_request trigger on .devcontainer/Dockerfile changes so that a
Dockerfile-modifying PR gets a full build-test cycle before merge.

The "Tag and push" step is guarded by `github.event_name != 'pull_request'`
so nothing is ever published to GHCR during a PR run.
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