[
https://issues.jenkins-ci.org/browse/JENKINS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Hansche reassigned JENKINS-12881:
-------------------------------------
Assignee: rsandell (was: Joe Hansche)
The pull request is at
https://github.com/jenkinsci/gerrit-trigger-plugin/pull/12
The comment there is expanding on what I think is your initial suggestion in
the Confluence discussion (?), and I like the flexibility of being able to do
that. Just not sure how to really do cross-plugin support like that
(relatively new to Jenkins development). I've tested this, and it works, but
it's not as flexible as I'd like, since some of the failures will be caused by
post-build steps, where a shell script won't be able to manipulate the
error-message file.
This also kind of creates some ambiguity, because it's possible for the
error-message file to exist in the workspace (e.g., from an old build?), and
that could cause the file to get picked up in a later build that actually
failed as a result of a publisher, for example -- and that would be misleading
in the Gerrit comment. So, not really sure how I feel about this yet.
> Allow reading custom build message from a workspace file, in case of
> non-success
> --------------------------------------------------------------------------------
>
> Key: JENKINS-12881
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12881
> Project: Jenkins
> Issue Type: New Feature
> Components: gerrit-trigger
> Affects Versions: current
> Reporter: Joe Hansche
> Assignee: rsandell
> Labels: gerrit
>
> Some background is discussed here:
> https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger?focusedCommentId=59508437#comment-59508437
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
