moncic-ci yaml parsing

[brancomat]

Our CI procedures (will) use .moncic-ci.yml files saved in various github projects, e.g.: https://github.com/ARPA-SIMC/moncic-ci/blob/main/.moncic-ci.yml:

version: 1
images:
 - name: fedora:34

version is mandatory, images is optional and defines the list of distro:version that the CI should build the project on. If omitted it implies "all of them", the full list is defined on the CI server.

The current CI procedure will then launch a parallel build for each distro/version, saving:

• the complete build log
• the exit status for each build
• a global exit status (0 if every build succeeded)

As discussed earlier with @edigiacomo and @spanezz we could implement this behaviour directly in moncic-ci as a possible enhancement (in that case, moncic-ci yaml specifications should be documented somewhere in this repo)

[edigiacomo]

For each distro/version we should be able to set a timeout beyond which the single build must be terminated. We could have a default timeout value (like the list of images) and maybe a max value too: max value > yaml value > default value.

[spanezz]

This is likely turning into a new option for moncic-ci, where it automates several build commands in parallel. I'd be tempted to rename the current ci in build, and implement this as ci.

This also means saving the logs of each builds separately in some destinations, and setting up builds differently depending on distributions (with the debian ones requiring a temporary merge with the debian/* or ubuntu/* branches).

I propose to specifiy the broader problem space into a practical config/implementation proposal, and then trying to implement it. I'd need your input in the proposal, since you're the Custodians of Use Cases