Remove unused GITHUB_TOKEN build argument from Dockerfiles#66
Conversation
The setup-build-system stage declared ARG GITHUB_TOKEN at the top, even though the token is only used in run-app (gh release download). Since CI passes a per-run secrets.GITHUB_TOKEN via --build-arg and that value changes every workflow run, the ARG invalidated every layer downstream in setup-build-system and compile-openms — apt-get update and all package installs re-ran from scratch on every PR/push. This is the same fix as 859e481 ("fix(docker): stop cache-busting on GITHUB_TOKEN"); the merge in a723fb5 left both copies of the ARG in place (the redundant one at line 34 and the one actually needed in run-app at line 217). Keep only the run-app declaration. Applies to both Dockerfile and Dockerfile.arm.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughBuild arguments across Docker stages are reorganized to improve configuration scoping. The main Dockerfile adds OpenMS repository, branch, and port configuration arguments to the setup-build-system stage, while removing GITHUB_TOKEN from that stage where it is unused. Dockerfile.arm removes the same token argument from setup-build-system. The token is redeclared only in the run-app stage where it is consumed. ChangesDocker Build Configuration
Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Removes the unused
GITHUB_TOKENbuild argument from bothDockerfileandDockerfile.arm. This argument was declared but never referenced in the build process.Changes
ARG GITHUB_TOKENdeclaration and its associated comment fromDockerfileARG GITHUB_TOKENdeclaration and its associated comment fromDockerfile.armDetails
The
GITHUB_TOKENargument was previously documented as being used "to download latest OpenMS executable for Windows from Github action artifact," but this functionality is not actually utilized in the current Docker build configuration. TheGITHUB_USERandGITHUB_REPOarguments remain, as they are still in use for artifact downloads.This cleanup reduces unnecessary build arguments and potential security concerns around token handling in Docker builds.
https://claude.ai/code/session_015kE3xopcwc6muQr9dfrLtY
Summary by CodeRabbit
Chores