Before merging any compose configuration change, we should be able to verify how the resulting compose changes. For example, when adding new packages to a comps file, we should be able to see all the packages pulled-in as dependencies and we should also ensure this compose passes basic sanity tests.
The C4 tool takes following inputs:
The C4 tool then uses this input to create two minimal composes using the ODCS (On Demand Compose Service):
The C4 tool compares these two composes and prints the difference to stdout.
The plan is to have the Jenkins Job running the C4 tool on any PR against pungi-fedora, comps and module-defaults repositories. The summary of compose difference will be added as comment to the PR.
It should therefore be clear if the most important parts of the compose still works with the PR applied and how the PR changed the compose.