-
Notifications
You must be signed in to change notification settings - Fork 180
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
Bump version to 5.1.0 and clean the spec files #9221
Conversation
👋 Hello! Thanks for contributing to our project. If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code. Reference tests: KNOWN ISSUES Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience. For more tips on troubleshooting, see the troubleshooting guide. Happy hacking! |
13d00eb
to
e087114
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.
Looks to be OK in general. Left some comments.
Since the PR is huge, could be I missed something, but we should be able to detect it when we try to build all the stuff.
containers/proxy-httpd-image/proxy-httpd-image.changes.releng.bump
Outdated
Show resolved
Hide resolved
containers/proxy-salt-broker-image/proxy-salt-broker-image.changes.releng.bump
Outdated
Show resolved
Hide resolved
containers/proxy-squid-image/proxy-squid-image.changes.releng.bump
Outdated
Show resolved
Hide resolved
schema/spacewalk/upgrade/susemanager-schema-5.0.10-to-susemanager-schema-5.1.0/.gitkeep
Outdated
Show resolved
Hide resolved
@deneb-alpha not in this PR, but we should not forget to change the ProjectConfig of D:G:M:H Macros: |
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.
Nothing to review from frontend.
yes, as soon as the PR will be ready to be merged I'll have to adapt both Head and Uyuni:Master |
- Move to RELEASE_STAGE=beta for setting the proper labels on the containers - Update the rhn_web.conf to web.version = 5.1.0 Alpha1 - Update the rhn_web.conf to web.version.uyuni = 2024.09 - Update INIT_BASE in the Dockerfiles from opensuse/leap:15.5 to opensuse/leap:15.6 - Update BASE in Dockerfiles from bci-base:15.5 to bci-base:15.6 - Add migration paths from 5.0 to 5.1
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.
As the PR is huge, I only reviewed again the missing schema migrations, not the whole PR again.
Looks good.
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.
just one small nitpick
In order not to trust the script blindly, even after so many reviews, I've run this command, from Marina's fork (see end of the message). No rests of 5.0.X, which is a good sign. Continuing review.
|
This PR is huge to review, I've added checkboxes in the description for each item before approving. A tick means a review from me. |
BASE changed to 15.6 everywhere for the dockerfiles:
|
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, approving (see my last comments for details).
What does this PR change?
spec-cleaner
RELEASE_STAGE=beta
for setting the proper labels on the containersrhn_web.conf
toweb.version = 5.1.0 Alpha1
rhn_web.conf
toweb.version.uyuni = 2024.09
INIT_BASE
in the Dockerfiles fromopensuse/leap:15.5
toopensuse/leap:15.6
BASE
in Dockerfiles frombci-base:15.5
tobci-base:15.6
containers/proxy-systemd-services/uyuni-proxy-systemd-services
has been also bumped, but it should directly be dropped for 5.1 and Uyuni 2024.09. See also https://github.com/SUSE/spacewalk/issues/23356 I didn't do directly here because this PR is quite huge already and it could make sense to drop this package in a new PR.GUI diff
No difference.
Documentation
No documentation needed: only internal and user invisible changes
DONE
Test coverage
ℹ️ If a major new functionality is added, it is strongly recommended that tests for the new functionality are added to the Cucumber test suite
No tests: only spec files changes built in:
DONE
Links
relates: https://github.com/SUSE/spacewalk/issues/25152
Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:
If you uncheck the checkbox after the PR is created, you will need to re-run
changelog_test
(see below)Re-run a test
If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:
Before you merge
Check How to branch and merge properly!