flo-renaud
commented
3 weeks ago Hi @vojtechsokol I picked your commit in my PR: https://github.com/oamg/leapp-repository/pull/1273 and added a short url for the 9-to-10 migration guide.
The creation of the final link will be handled in the ticket OAMG-11275.
pirat89
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. If you want to request a review or rebuild a package in copr, you can use following commands as a comment:
review please @oamg/developersto notify leapp developers of the review request/packit copr-buildto submit a public copr build using packitPackit will automatically schedule regression tests for this PR's build and latest upstream leapp build. However, here are additional useful commands for packit:
/packit testto re-run manually the default tests/packit retest-failedto re-run failed tests manually/packit test oamg/leapp#42to run tests with leapp builds for the leapp PR#42 (default is latest upstream - master - build)Note that first time contributors cannot run tests automatically - they need to be started by a reviewer.
It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported,
beaker-minimalandkernel-rt, both can be used to be run on all upgrade paths or just a couple of specific ones. To launch on-demand tests with packit:/packit test --labels kernel-rtto schedulekernel-rttests set for all upgrade paths/packit test --labels beaker-minimal-8.10to9.4,kernel-rt-8.10to9.4to schedulekernel-rtandbeaker-minimaltest sets for 8.10->9.4 upgrade pathSee other labels for particular jobs defined in the
.packit.yamlfile.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.