-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Remove 'docker' from the names of the Docker images published on ghcr.io #35079
Conversation
The "build" workflows fail here exactly because of the rename -- it cannot fetch the prebuilt image because it now expects a different name. |
If this is merged as is, do then not all PRs based on the develop will fail as well until the required images are build and published? Maybe split this PR into two stages: first publish images under the new name, second use the new images in the workflows/devcontainer? |
I think this is a minor concern because of the way that we merge: develop is only advanced at the push of the next beta tag. This triggers the the necessary image build. |
But I don't mind splitting it up. |
43edbf0
to
18f4210
Compare
Here we go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code-wise looks good to me. But docker doesn't run on my system atm, so I don't have a way to test this out.
Thanks! |
Codecov ReportBase: 88.60% // Head: 88.59% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #35079 +/- ##
===========================================
- Coverage 88.60% 88.59% -0.02%
===========================================
Files 2136 2136
Lines 396142 396142
===========================================
- Hits 350990 350948 -42
- Misses 45152 45194 +42
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
do we want this to go to develop now? |
Yes, ASAP, but I think you'll need to coordinate with @vbraun |
Sorry, made a stupid mistake. Fixed now (see https://github.com/users/mkoeppe/packages?repo_name=sage) |
… in the name <!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes #1234" use "Introduce new method to calculate 1+1" --> ### 📚 Description <!-- Describe your changes here in detail --> Step 2 of the rename done in #35079. <!-- Why is this change required? What problem does it solve? --> Step 2 make sure that multi-stage workflows and devcontainers use the most current image, not the last image before the migration. The "build" and "build-doc" workflows will be updated in a 3rd (and final) step. <!-- If it resolves an open issue, please link to the issue here. For example "Closes #1337" --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I have made sure that the title is self-explanatory and the description concisely explains the PR. - [ ] I have linked an issue or discussion. - [ ] I have created tests covering the changes. - [x] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- List all open pull requests that this PR logically depends on --> <!-- - #xyz: short description why this is a dependency - #abc: ... --> This should only be merged when the images with the new names have been pushed. URL: #35080 Reported by: Matthias Köppe Reviewer(s): Dima Pasechnik
… in the name (step 3) <!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes #1234" use "Introduce new method to calculate 1+1" --> ### 📚 Description Step 3 of the rename done in #35079 and #35080. This will speed up the "Build & Test" and "Build documentation" workflows because they will start from more recent images. <!-- Describe your changes here in detail --> <!-- Why is this change required? What problem does it solve? --> <!-- If it resolves an open issue, please link to the issue here. For example "Closes #1337" --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I have made sure that the title is self-explanatory and the description concisely explains the PR. - [x] I have linked an issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- List all open pull requests that this PR logically depends on --> <!-- - #xyz: short description why this is a dependency - #abc: ... --> URL: #35278 Reported by: Matthias Köppe Reviewer(s): Dima Pasechnik
📚 Description
We shorten the names of the Docker images generated by our portability tests slightly by removing the redundant word
docker
from it.This is done because the previously used names still belong to the old repository (which is now renamed as sagemath/sage-archive-...), and the new repository does not have permissions to push new versions there.
This can be changed package by package in the web interface, but there is no API for doing so and we have over 1000 packages. So instead we change the naming pattern; the removal of the redundant word is a welcome side effect.
📝 Checklist
⌛ Dependencies