Re: [openstack-dev] [Sahara][infra] Jenkins based 3rd party CIs
On Monday, 6 March 2017 20:05:18 CET James E. Blair wrote: > Telles Nobrega writes: > > Hello, > > > > we from Sahara use the compatibility layer with Zuulv2.5 and we are > > wondering if with the change to Zuulv3 this compatibility layer will still > > be maintained. > > If the layer is removed it will reflect into some changes on our side and > > we are looking for this information to identify how much work will be > > needed on our CI. > > Hi, > > If you are referring to the ability to run jobs in Jenkins, no, Zuul > will no longer have direct support for that. Hi, just to be more clear: does it affect 3rd-party CIs still using Jenkins? The current Sahara CI (see http://git.openstack.org/cgit/openstack/sahara-ci-config) uses Jenkins and a local Zuul installation. I have to admit I lack some knowledge on how much the job triggering is connected to the main instance, so apologize for the stupid question: if we keep our configuration as it is now, will it continue to work? (not talking about the convenience of switching to zuul v3, as 2.x is going to be unmaintained, this is just to set the priorities). -- Luigi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Sahara][infra] Jenkins based 3rd party CIs
Telles Nobrega writes: > Hello, > > we from Sahara use the compatibility layer with Zuulv2.5 and we are > wondering if with the change to Zuulv3 this compatibility layer will still > be maintained. > If the layer is removed it will reflect into some changes on our side and > we are looking for this information to identify how much work will be > needed on our CI. Hi, If you are referring to the ability to run jobs in Jenkins, no, Zuul will no longer have direct support for that. If you are asking about using the zuul-launcher in Zuul v2.5 (which reads job configurations in jenkins-job-builder and uses Ansible to run jobs in the same way that Jenkins would), we won't have direct support for that either (this is part of the reason we are not encouraging people to use that). However, in *either* case, we do expect to have some kind of automated process to convert many jobs written in JJB. Much of the code that we wrote for Zuul v2.5 to translate JJB into Ansible should be able to be reused for that purpose. The output may not be optimal -- it will likely be a series of bulky Ansible shell tasks, but we hope it will accomplish much of the work in an automated fashion so that an operator will be able to improve the result over time. You may wish to keep an eye out for periodic updates to our progress that Robyn Bergeron is planning to send out, such as this one: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113148.html -Jim __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Sahara][infra] Jenkins based 3rd party CIs
Hello, we from Sahara use the compatibility layer with Zuulv2.5 and we are wondering if with the change to Zuulv3 this compatibility layer will still be maintained. If the layer is removed it will reflect into some changes on our side and we are looking for this information to identify how much work will be needed on our CI. Thanks, __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
