-
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
Use the full container version for build_version #1982
base: main
Are you sure you want to change the base?
Conversation
Created a staging project on OBS for 5: home:defolos:BCI:Staging:SLE-15-SP5:5-1982 |
Created a staging project on OBS for 7: home:defolos:BCI:Staging:SLE-15-SP7:7-1982 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-1982/ 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-1982 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-1982/ tox -- -n auto The following images can be pulled from the staging project:
|
4b45ea7
to
6a32e01
Compare
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.
we're expecting tag_version to be used in various places, e.g. the openqa scripts. I wonder if it wouldn't be simpler to use forcemultiversion instead and then go with buildrelease?
# first try to use the containers full version, if that fails, pick | ||
# tag_version and if that also fails, fall back to the parent's classes | ||
# version |
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.
so that means switching from a %%..
%%` based version to another version will change the behavior. is that really a good idea? seems very dangerous to me.
I think the current setup of "version" being the %%placeholder and "tag_version" being a placeholder-free "stable" version is good enough and more predictable in behavior. I know we fscked it up for kiwi but that has been fixed and there is now a check that tag_version needs to be set if there is a placeholder in version. we could enforce it even more to have tag_version always set which I think would make the behavior more predicatble.
No description provided.