ci: use rancher head version instead of rc version #853
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #720
In the CI, we don't really test latest rancher version but release candidate version.
It could be better to test latest updates, that's why we want to test
v2.7-head
by default.Older behavior
When we set
rancherVersion
tolatest/devel
, it installed latest rc version.New behavior
With
rancherVersion
equal tolatest/devel
, we install the head version (by default)With
rancherVersion
equal tolatest/2.7.5-rc3
, we install 2.7.5 release candidate 3PS: The head version is hardcoded but I don't know if we can make it better without adding a new variable, could be improve later.
Verification runs
rancherVersion
set tolatest/2.7.5-rc3
https://github.com/rancher/elemental/actions/runs/5141439434/jobs/9253956631I checked the pod image and it was ok:
UI-K3s-Rancher_Latest: failed because there is a login issue with
v2.7.5-rc3
but the logic is ok.rancherVersion
set tolatest/devel
(default choice)https://github.com/rancher/elemental/actions/runs/5142244935/jobs/9255751656
UI-K3s-Rancher_Latest: we can see that v2.7-head was used.