I'd like to be able to know what gerrit comment caused that particular event trigger. At the moment the gerrit comment is processed in this class "src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/events/PluginCommentAddedEvent.java" b and the build parameter GERRIT_EVENT_TYPE contains 'comment-added' but the gerrit comment value is not exported.

 

As a D I'd like to be able to have one single Gerrit Server Jenkins entry point and customise the Gerrit workflow within Jenkins, so people can command actions based on regex and filter them based on different subset of regext, for instance:

• One Gerrit Jenkins server
• One Jenkins Job listening for Gerrit events based on the comment added with certain regex
  • automateme (build|test|deploy|release)
• Some Jenkins Job logic will add further actions based on the commands:
  • build
  • test
  • deploy
  • release

At the moment, I can implement something similar but with 4 different Jenkins jobs, which are listening Gerrit events for the below regex:

• automateme build
• automateme test
• automateme deploy
• automateme release