Open Stack

On 2018-08-31 20:41, Clark Boylan wrote:
> Hello,
> 
> OpenStack is currently in the process of migrating project CI job configs into individual repos. Part of the motivation for this was to remove us (the Infra team) as a roadblock to getting job config changes merged. This is particular important for OpenStack as it is trying to update its job configs to be python3 first so there will be a fair bit of job churn over the Stein cycle.
> 
> This is great for OpenStack, but the question has come up about whether or not we (the Infra team) want to do similar for our projects.
> 
> My initial thought is that it isn't as urgent for us because infra-core already manage both the separate repos and the central job config. This means we can manage the job churn ourselves regardless of the location. Considering the other items we currently have on our place (namely Winterscale and config management updates) I'm willing to defer on this for now.
> 
> If you think we should make moving job config into our repos a priority please let me know. More than happy to accommodate this work, but we will likely need a volunteer to help do it. (I don't expect we'll be able to piggy back off of the OpenStack work as we have many non standard jobs from OpenStack's perspective).

Moving the jobs in repo is not that difficult - updating them all to use 
python3 will be. The scripts by Doug will help us a lot.

Still, for our 158 repositories, I don't see the benefit at the moment 
since it's the same team dealing with it and as Clark said we have some 
other things on the plate. We can do this for repos where - and once - 
it makes sense one by one over time as we did already,

Andreas
-- 
  Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
        HRB 21284 (AG Nürnberg)
     GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126