Re: Updating gerrit.ovirt.org version

Fyi, Jenkins Gerrit Trigger plugin has a new version [1] 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 2.2.2.1. Do we have plans on upgrading gerrit in the near future?

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 commit, 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. [1] https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger <snippet> ... 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 started. This will be used to filter out functionality that is not available in all Gerrit versions. 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 project/branch. 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. ... </snippet> Eyal Edri