|[cross-project-issues-dev] Gerrit and Jenkins, tips and news|
For those of you who use a JIPP to build Gerrit patch sets, you may have noticed that the user "Hudson CI" has been renamed to "CI Bot". This is purely cosmetic.
Also, the documentation about how to setup the Gerrit trigger Jenkins plugin has been revamped and is now available here https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin
I would like to draw you attention to the possible triggers you can setup (https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers). Many of you want to re-trigger a build when it fails (e.g., because of flaky tests). It can be tedious to have to go to Jenkins just to do that. The Gerrit trigger Jenkins plugin is not only able to trigger a build on a new patch set. It lets you define triggers on comment values (e.g., if a comment contains "run CI"). Have a look at the previous link for an example.
Mikaël Barbero - Eclipse Foundation
IT Services - Release Engineering
📱 (+33) 642 028 039
Description: Message signed with OpenPGP
Back to the top