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

Remove 'docker' from the names of the Docker images published on ghcr.io #35079

Merged
merged 2 commits into from
Mar 13, 2023

Conversation

mkoeppe
Copy link
Contributor

@mkoeppe mkoeppe commented Feb 12, 2023

📚 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

  • 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.
  • I have updated the documentation accordingly.

⌛ Dependencies

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Feb 12, 2023

The "build" workflows fail here exactly because of the rename -- it cannot fetch the prebuilt image because it now expects a different name.

@tobiasdiez
Copy link
Contributor

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?

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Feb 12, 2023

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.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Feb 12, 2023

But I don't mind splitting it up.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Feb 12, 2023

Here we go.

Copy link
Contributor

@tobiasdiez tobiasdiez left a 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.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Feb 12, 2023

Thanks!

@codecov-commenter
Copy link

codecov-commenter commented Feb 12, 2023

Codecov Report

Base: 88.60% // Head: 88.59% // Decreases project coverage by -0.02% ⚠️

Coverage data is based on head (118f756) compared to base (c000c95).
Patch has no changes to coverable lines.

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     
Impacted Files Coverage Δ
src/sage/interfaces/qsieve.py 71.30% <0.00%> (-2.61%) ⬇️
...e/combinat/cluster_algebra_quiver/mutation_type.py 50.59% <0.00%> (-2.14%) ⬇️
src/sage/modular/local_comp/liftings.py 98.33% <0.00%> (-1.67%) ⬇️
src/sage/schemes/elliptic_curves/hom_velusqrt.py 94.09% <0.00%> (-1.58%) ⬇️
src/sage/modular/hecke/algebra.py 94.65% <0.00%> (-1.07%) ⬇️
src/sage/combinat/posets/poset_examples.py 87.67% <0.00%> (-0.86%) ⬇️
src/sage/coding/channel.py 97.10% <0.00%> (-0.73%) ⬇️
src/sage/graphs/generators/random.py 91.95% <0.00%> (-0.69%) ⬇️
src/sage/groups/generic.py 88.34% <0.00%> (-0.68%) ⬇️
...sage/geometry/hyperbolic_space/hyperbolic_model.py 88.95% <0.00%> (-0.62%) ⬇️
... and 15 more

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.
📢 Do you have feedback about the report comment? Let us know in this issue.

Copy link
Member

@dimpase dimpase left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@dimpase
Copy link
Member

dimpase commented Feb 12, 2023

do we want this to go to develop now?

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Feb 12, 2023

do we want this to go to develop now?

Yes, ASAP, but I think you'll need to coordinate with @vbraun

@dimpase
Copy link
Member

dimpase commented Feb 12, 2023

@vbraun - can we get this merged into develop now? - and another build related PR, #34984 ?

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Feb 12, 2023

Sorry, made a stupid mistake. Fixed now (see https://github.com/users/mkoeppe/packages?repo_name=sage)

@vbraun vbraun merged commit 1aa2370 into sagemath:develop Mar 13, 2023
@mkoeppe mkoeppe added this to the sage-10.0 milestone Mar 13, 2023
vbraun pushed a commit that referenced this pull request Mar 26, 2023
… 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
vbraun pushed a commit that referenced this pull request Apr 1, 2023
… 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants