-
Notifications
You must be signed in to change notification settings - Fork 21
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
mark more images as singleton image #2302
Conversation
We were actually not stripping the version, which led to unstable buildnames and a ton of aggregate updates all the time.
Created a staging project on OBS for 7: home:defolos:BCI:Staging:SLE-15-SP7:7-2302 Build ResultsRepository
Repository
Repository
Repository
Repository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=15.7 TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/sle-15-sp7/7-2302/ tox -- -n auto The following images can be pulled from the staging project:
|
Created a staging project on OBS for 6: home:defolos:BCI:Staging:SLE-15-SP6:6-2302 Build ResultsRepository
Repository
Repository
Repository
Repository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=15.6 TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/sle-15-sp6/6-2302/ tox -- -n auto The following images can be pulled from the staging project:
|
We lost a couple of months of image updates because the aggregates were not updated. Lets have a stable buildname to avoid this going forward.
7bc1c5d
to
48c21f5
Compare
Created a staging project on OBS for 16.0: home:defolos:BCI:Staging:16.0:16.0-2302 |
We have two different kiwi major versions between sle15 and sle16, would this work for that case? Others might be single images, although I am not hundred percent sure spack will stay this way. |
Yes. we only need versions in the build name if the container is maintained in parallel from the same codestream, which isn't the case here.
There is no harm with changing it to not be a singleton image anymore once that is the case. we'll have most pain with renaming the source package container (and the loss of build counter etc). |
No description provided.