standard CI packages files

[Barak Korren]

On 12 March 2018 at 09:55, Yedidyah Bar David <didi at redhat.com> wrote:
> Hi all,
>
> The various automation/*.packages* files are rather hard to maintain -
> with many partial duplicates, symlinks, and changes applied to some
> file forgotten to be applied to others that needed them.
>
> Can we have something more dynamic? E.g. that CI will run a single
> script, e.g. automation/get-needed-packages, provide it as args the
> action to be ran ("check-patch", "build-artifacts" etc.) and the
> distro ("el7", "fc27" etc.) and use whatever it outputs as the list of
> packages to install?
>

The problem with this approach is that its a slippery slope - because
the script to calculate the packages might need packages of its own to
run...

In STDCI V2 we laid the groundwork for using a single YAML file to
specify everything, this will open up the possibility of using YAML
inheritance and macros to share specification parts between different
jobs. I think that can be a good enough compromise.

-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted