DoDiODev opened a new pull request, #9267: URL: https://github.com/apache/devlake/pull/9267
### Summary Follow-up to #9209 and the [dev@ discussion](https://lists.apache.org/[email protected]). `build-builder.yml` pushed the CI toolchain image to `mericodev/lake-builder` with separate credentials, so that image has not been updated since 2023-06-30. As agreed on the list, it now publishes to the `apache` namespace: - Same Docker Hub credentials and owner as `build.yml` (`DOCKERHUB_USER` / `DOCKERHUB_TOKEN` / `DOCKERHUB_OWNER`). - Still triggered by a `builder-v*` git tag; pushing `builder-v0.0.16` publishes `apache/devlake:lake-builder-v0.0.16`. A tag in the existing `apache/devlake` repository needs no new Docker Hub repository. - No moving `latest` tag. Workflows will pin an explicit version. - Buildx/login/build-push actions use the same pinned SHAs as `build.yml`, so they are already on the ASF allowlist. The job only runs in `apache/devlake`. - `devops/docker/lake-builder/README.md` updated accordingly; the manual `mericodev` push instructions are removed. This PR does not change any existing CI job. After it is merged, a committer needs to push the first tag: ```shell git tag builder-v0.0.16 && git push origin builder-v0.0.16 ``` v0.0.16 continues the numbering of the last `mericodev` image (v0.0.15). A follow-up PR then points the five `container: mericodev/lake-builder:latest` lines (unit-test, e2e mysql/postgres, golangci-lint, migration-script-lint) to `apache/devlake:lake-builder-v0.0.16`. ### Does this close any open issues? Part of #9209 (the follow-up PR will close it). ### Other Information Checked with `actionlint`. The current `devops/docker/lake-builder/Dockerfile` (Go 1.27.3, libgit2 1.5.0, bookworm) is built in my fork's CI and runs the unit, lint and e2e tests there. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
