[openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test

Roey Chen roeyc at mellanox.com
Mon Jan 20 21:21:03 UTC 2014


You can get the information you want from the environment variables that the Gerrit plugin sets.

Just like it was mentioned here: https://etherpad.openstack.org/p/multi-node-neutron-tempest
if you'll set NEUTRON_BRANCH=$GERRIT_REFSPEC in the localrc
then Devstack will pull the change which triggered the build.

Try env shell command to find out what are the rest of the environment variables.


From: Mohammad Banikazemi [mb at us.ibm.com]
Sent: Monday, January 20, 2014 9:32 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [neutron] [third-party-testing] Which patchset triggered the test

Have a question regarding the Jenkins/Gerrit setup for third party testing setups.

When Jenkins get triggered by a patchset through the Gerrit trigger plug-in, you can execute a set of shell scripts. How do you get the information about the patchset that triggered the test? In particular, in your scripts how do you figure out which patchset triggered the test. Here is why I am asking this question:
During our earlier IRC calls we said, one approach for testing would be using devstack to install OpenStack and run appropriate tests. The devstack stack.sh brings in the master branch without the patchset which triggered the test. How do I access the patchset I want to test? Am I missing something here?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140120/b3869ea8/attachment.html>

More information about the OpenStack-dev mailing list