[openstack-dev] [third-party] [ci] Please PIN your 3rd party ci setup to JJB 1.6.1
ramy.asselin at hpe.com
Fri Aug 5 18:28:51 UTC 2016
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 ) as shown here 
Re-run puppet (sudo puppet apply --verbose /etc/puppet/manifests/site.pp ) and that will ensure your JJB & zuul installations are pinned to stable versions.
 diff: https://review.openstack.org/#/c/348035/4/contrib/single_node_ci_data.yaml
 full: http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/single_node_ci_data.yaml
From: Asselin, Ramy
Sent: Friday, July 08, 2016 7:30 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [third-party] [ci] Upcoming changes to Nodepool for Zuul v3
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.
From: Monty Taylor [mailto:mordred at inaugust.com]
Sent: Thursday, July 07, 2016 6:21 PM
To: openstack-infra at lists.openstack.org
Subject: [OpenStack-Infra] Upcoming changes to Nodepool for Zuul v3
tl;dr - nodepool 0.3.0 tagged, you should pin
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:
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.
OpenStack-Infra mailing list
OpenStack-Infra at lists.openstack.org
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev