On Tue, Jan 09, 2018 at 02:29:38PM +0100, Dan Horák wrote: > On Tue, 9 Jan 2018 11:03:28 +0100 > Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > > > Dear all, > > > > The Fedora Infrastructure team has had a jenkins instance running at > > jenkins.fedorainfracloud.org for a little while now. This instance was > > maintained on a best-effort basis though and we often had outage and > > issues when upgrading it. > > Originally the jenkins master was running on RHEL using the RPMs > > provided by upstream jenkins. When jenkins became available in > > Fedora, we switched our master to be Fedora using the RPMs from > > Fedora. However, nowadays Jenkins is no longer packaged for Fedora, > > our jenkins master is therefore outdated. > > > > On the other side of the fence, with our dear friends from CentOS, is > > a brand new, shiny and well supported Jenkins instance. > > So we thought it may be good to leverage the CentOS infrastructure to > > alleviate our infrastructure and maintenance. > > > > We are currently working on setting up a Jenkins master in > > ci.centos.org that would be dedicated to projects ran in pagure.io. > > It needs a small change to pagure.io and some work on the CentOS side > > but nothing hard and we expect to be able to migrate the first > > volunteer projects by early next week. > > do you plan to use the dynamically provisioned workers like the > current CentOS CI or will it use the static workers like the Fedora > Jenkins? My understanding is to start with static workers as we have now in Fedora to ease the migration (no config change needed) and work from there to migrate to dynamically provisioned workers as the rest of CentOS CI does. Pierre _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
