-
Notifications
You must be signed in to change notification settings - Fork 200
Always use RHCOS version from installer #778
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
Conversation
|
This could be an alternative to #766 |
|
Build FAILURE, see build http://10.8.144.11:8080/job/dev-tools/1109/ |
f9f3ce4 to
0df6722
Compare
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/1110/ |
0df6722 to
2975c76
Compare
|
cc @rlopez133 we discussed this approach for install-scripts |
|
looks good, we can see the CI pass used the right image: However I think there's a rebase mistake which accidentally reverts #776 ? |
hardys
left a comment
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.
Other than now needing a rebase, and possible optimization of not downloading rhcos.json in the source case (not blocking on that though) lgtm, thanks!
2975c76 to
ceb9867
Compare
Instead of hardcoding the RHCOS version in dev-scripts, by re-ordering some things like extracting/building the installer first, we can use the rhcos.json from the installer to find out which RHCOS version we should be using.
ceb9867 to
33667e6
Compare
|
Build SUCCESS, see build http://10.8.144.11:8080/job/dev-tools/1112/ |
|
Ready for another look, CI passed and I fixed it so it reads rhcos.json from the git repo if we're doing a source install. |
Instead of hardcoding the RHCOS version in dev-scripts, by re-ordering
some things like extracting/building the installer first, we can use the
rhcos.json from the installer to find out which RHCOS version we should
be using.