|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Using Gerrit-trigger 2.12.0 plugin on gerrit 2.8.7 and Jenkins ver. 1.559, the custom build message works as follows:
1. Gerrit trigger plugin has the default messages for all jobs defined
2. If a job has its custom build message defined, it is printed out after the default message
For example, the default message for build started is defined as: gerrit review <CHANGE>,<PATCHSET> --message 'Build started <STARTED_STATS>' --verified <VERIFIED> --code-review <CODE_REVIEW>
Then, the custom message for build started is defined as "Custom start message"
Result in gerrit:
Patch Set 1:
Build started
Custom start message
So the initial assumption of custom message overriding the default message seems to be wrong. I had the same impression that it would be possible to override the default, but no.