All, In the previous e-mail, [1] was recommending 3rd party ci to pin zuul to v. 2.1.0, but this has pip dependency conflicts with nodepool 0.3.0 when installed on the same VM (common case typical for 3rd party ci) causing zuul service to fail to start. This is fixed by using the newly created zuul v. 2.5.0 tag [2], which has compatible pip dependencies along with many bug fixes.
It is strongly recommended to apply this pins to your setup and NOT use master branch in order to keep you CI systems stable. The full set of recommended pins is being maintained in this file [3]. Ramy [1] https://review.openstack.org/#/c/348035/4/contrib/single_node_ci_data.yaml [2] https://review.openstack.org/#/c/352560/1/contrib/single_node_ci_data.yaml [3] http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/single_node_ci_data.yaml -----Original Message----- From: Asselin, Ramy Sent: Friday, August 05, 2016 11:29 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [third-party] [ci] Please PIN your 3rd party ci setup to JJB 1.6.1 All, In case you're still using JJB master branch, it is highly recommended that you pin to 1.6.1. There are recent/upcoming changes that could break your CI setup. You can do this by updating your puppet hiera file (/etc/puppet/environments/common.yaml [1]) as shown here [2][3] Re-run puppet (sudo puppet apply --verbose /etc/puppet/manifests/site.pp [1]) and that will ensure your JJB & zuul installations are pinned to stable versions. Ramy [1] http://docs.openstack.org/infra/openstackci/third_party_ci.html [2] diff: https://review.openstack.org/#/c/348035/4/contrib/single_node_ci_data.yaml [3] full: http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/single_node_ci_data.yaml -----Original Message----- From: Asselin, Ramy Sent: Friday, July 08, 2016 7:30 AM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [third-party] [ci] Upcoming changes to Nodepool for Zuul v3 All, If you haven't already, it's recommended to pin nodepool to the 0.3.0 tag and not use master. If you're using the puppet-openstackci solution, you can update your puppet hiera file as shown here: https://review.openstack.org/293112 Re-run puppet and restart nodepool. Ramy -----Original Message----- From: Monty Taylor [mailto:mord...@inaugust.com] Sent: Thursday, July 07, 2016 6:21 PM To: openstack-in...@lists.openstack.org Subject: [OpenStack-Infra] Upcoming changes to Nodepool for Zuul v3 Hey all! tl;dr - nodepool 0.3.0 tagged, you should pin Longer version: As you are probably aware, we've been working towards Zuul v3 for a while. Hopefully you're as excited about that as we are. We're about to start working in earnest on changes to nodepool in support of that. One of our goals with Zuul v3 is to make nodepool supportable in a CD manner for people who are not us. In support of that, we may break a few things over the next month or two. So that it's not a steady stream of things you should pay attention to - we've cut a tag: 0.3.0 of what's running in production right now. If your tolerance for potentially breaking change is low, we strongly recommend pinning your install to it. We will still be running CD from master the whole time - but we are also paying constant attention when we're landing things. Once this next iteration is ready, we'll send out another announcement that master is in shape for consuming CD-style. Thanks! Monty _______________________________________________ OpenStack-Infra mailing list openstack-in...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra __________________________________________________________________________ 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 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 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
