CLOS-3828: Combine repository mappings when setting up target repos #42
Conversation
Previously the code only considered a single repomap item - likely a leftover from upstream, where it's not expected that more than one exists. In our case it's quite likely, however, due to each vendor having their own repomap that may appear conditionally. Therefore, all available maps need to be merged before usage.
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. |
Previously the code only considered a single repomap item - looks like a leftover from upstream, where it's not expected that more than one exists.
In our case it's quite likely, however, due to each vendor having their own repomap that may appear conditionally. Therefore, all available maps need to be merged before usage.