Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin dev image version #383

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Pin dev image version #383

wants to merge 2 commits into from

Conversation

Geogouz
Copy link
Contributor

@Geogouz Geogouz commented Mar 11, 2025

Pin rucio-dev image using ARG TAG, with early failing if no tag is provided.

Also, previously, the workflow used github.repository_owner when constructing Docker image tags, which caused push failures if the GitHub username did not match the Docker Hub username. This commit switches to using the DOCKER_HUB_USERNAME secret for the base tag. This should not affect actually any official build process where both usernames are identical (hence, the Docker Hub namespace should remain correct). The change is mostly for dev support.

@Geogouz Geogouz changed the title Use DOCKER_HUB_USERNAME for Docker image namespace Pin dev image version Mar 12, 2025
Geogouz added 2 commits March 12, 2025 03:11
Previously, the workflow used `github.repository_owner` when constructing Docker image tags,
which caused push failures if the GitHub username did not match the Docker Hub username.
This commit switches to using the `DOCKER_HUB_USERNAME` secret for the base tag, ensuring
images are pushed to the correct Docker Hub namespace. This does not affect the official
build process where both usernames are identical.
Pin dev builds using ARG TAG, failing early if no tag is provided.
@Geogouz
Copy link
Contributor Author

Geogouz commented Mar 12, 2025

Although this pins the version for the dev image, as explained in #379, we need to change also the rucio-dev deployment process (to be able to use also the current master state properly). I will send a different PR for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants