Mohammad, 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. Best, --- Roey ________________________________ From: Mohammad Banikazemi [m...@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? Thanks, Mohammad
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
