Re: standard CI packages files

On Mon, Mar 12, 2018 at 10:42 AM, Barak Korren <bkorren(a)redhat.com&gt; wrote: > On 12 March 2018 at 09:55, Yedidyah Bar David <didi(a)redhat.com&gt; 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... I see your point, but not sure it's a real problem. > > 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. Perhaps. When will we have this?