-
Notifications
You must be signed in to change notification settings - Fork 148
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
Add 79to88 and 79to89 aws upgrade paths + 79to810 and 810to94 #1145
Conversation
Thank you for contributing to the Leapp project!Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build. If you need a different version of leapp from PR#42, use It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported,
[Deprecated] To launch on-demand regression testing public members of oamg organization can leave the following comment:
Please open ticket in case you experience technical problem with the CI. (RH internal only) Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra. |
I guess this one will also be blocked on infra issues :( |
/packit test |
/packit test --labels sanity |
47ef751
to
3c668ec
Compare
Now it should be ok, all aws upgrade paths are here. |
Thanks to the detailed downstream review by mmoran I have realised that upstream upgrade paths have to be revised and updated as well. Also change identifier for the dot notation in the upgrade paths.
ffa1512
to
c322345
Compare
Thanks to the detailed downstream review by mmoran I have realised that upstream upgrade paths have to be revised and updated as well.