[openstack-dev] [puppet] introducing upgrade testing jobs

Emilien Macchi emilien at redhat.com
Fri Jun 26 16:15:22 UTC 2015


In case you've missed it, we have now voting functional testing jobs.
For example, if you submit a patch in puppet-keystone, it will deploy
keystone on both Ubuntu Trusty & CentOS7, and test that it works, by
using Beaker framework [1].

[1] https://github.com/puppetlabs/beaker-rspec

We would like to move forward and test that a patch does not break the
previous version of the module.

We are experimenting this workflow for now:
* clone HEAD^1 from the patchset (might change after our Kilo release)
* run acceptance
* checkout the patchset
* run acceptance

If tests pass, we will consider the patch does not break the previous
version of the module.

All of this is very experimental and any feedback is welcome.
For example, I think in the future (after our kilo release) we might
want to first test on stable/kilo and then test the patchset that will
really upgrade OpenStack.

Also, this job is experimental now, which means it's non-voting. Though
I would ask to people to consider failing jobs.

Emilien Macchi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150626/c7b16fa6/attachment.pgp>

More information about the OpenStack-dev mailing list