On 03/11/2012 10:40 AM, Eyal Edri wrote:
Jenkins Gerrit Trigger plugin has a new version  that support
Triggering commits based on their path (e.g. backend/*).
This feature requires a newer version of gerrit (we have currently 2.2.1), there is a
newer version 220.127.116.11.
Do we have plans on upgrading gerrit in the near future?
looks like it has a new prolog workflow engine which could be
interesting to utilize to make sure reviewer from multiple sub
components of engine review a patch, etc.
I have no problem upgrading to it, but would feel better if someone will
do a preliminary test with it not on the main gerrit.ovirt.org
Eyal - can you do so some sanity checking to this version from your side
(check your flows with doron maybe)?
This can help us trigger tests on gerrit patches only on specific commits.
for example, if we'll have a long test that we don't want to trigger on each
the developer can create a dir/file that jenkins will look for and only trigger the build
if it exists.
Or if we have limited jenkins resources, and we only want to tests one part of the code.
Version 2.5.0 (released Mar 8, 2012)
Features and Fixes
Gerrit version checking.
The plugin fetches the version of Gerrit each time the connection to Gerrit is
This will be used to filter out functionality that is not available in all
If a snapshot of Gerrit is used, all functionality will be enabled (as of today,
only the file path triggering below uses the version check).
JENKINS-12836 Add a Descriptor for the Branch to avoid a warning in the logs.
File path triggering.
One or more file paths can now be entered in the config of a Jenkins project, in
the same way as Gerrit project/branch.
The build will only trigger if the path is found in the patch set for this
Useful for big gits with lots of smaller modules beneath it.
Custom message from workspace file.
A workspace file can now be updated with information that will be sent in the
message from the trigger to Gerrit.