-
Improvement
-
Resolution: Unresolved
-
Major
-
None
The Build Failure Analyzer plugin provides some very handy information. I'd love to be able to include this information in the email notices that Jenkins sends out when builds fail, so that our developers can sometimes save time by not having to log in to Jenkins to see why a build failed.
The Jenkins email-ext plugin allows administrators to construct the email body contents using a series of tokens. Could Build Failure Analyzer provide a token that lists the failure analysis reasons, descriptions, and links to the indications?
[JENKINS-17658] Provide a token so that build failure causes can be included in build failure emails
| Description |
Original:
The Build Failure Analyzer plugin provides a very handy information. I'd love to be able to include this information in the email notices that Jenkins sends out when builds fail, so that our developers can sometimes save time by not having to log in to Jenkins when a build fails. The Jenkins email-ext plugin allows administrators to construct the email body contents using a series of tokens. Could Build Failure Analyzer provide a token that lists the failure analysis reasons, descriptions, and links to the indications? |
New:
The Build Failure Analyzer plugin provides some very handy information. I'd love to be able to include this information in the email notices that Jenkins sends out when builds fail, so that our developers can sometimes save time by not having to log in to Jenkins when a build fails. The Jenkins email-ext plugin allows administrators to construct the email body contents using a series of tokens. Could Build Failure Analyzer provide a token that lists the failure analysis reasons, descriptions, and links to the indications? |
| Description |
Original:
The Build Failure Analyzer plugin provides some very handy information. I'd love to be able to include this information in the email notices that Jenkins sends out when builds fail, so that our developers can sometimes save time by not having to log in to Jenkins when a build fails. The Jenkins email-ext plugin allows administrators to construct the email body contents using a series of tokens. Could Build Failure Analyzer provide a token that lists the failure analysis reasons, descriptions, and links to the indications? |
New:
The Build Failure Analyzer plugin provides some very handy information. I'd love to be able to include this information in the email notices that Jenkins sends out when builds fail, so that our developers can sometimes save time by not having to log in to Jenkins to see why a build failed. The Jenkins email-ext plugin allows administrators to construct the email body contents using a series of tokens. Could Build Failure Analyzer provide a token that lists the failure analysis reasons, descriptions, and links to the indications? |
hugo fonseca
added a comment - +1 please sorry, I thought I had a solution for this, but it does not work yet
Adam Guja
added a comment - - edited sorry, I thought I had a solution for this, but it does not work yet FWIW, I've tossed up a quick and dirty PR for this at https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/7 - doesn't have the links, and probably needs a lot more work to actually be useful, but it's a starting point.
Code changed in jenkins
User: K. R. Walker
Path:
pom.xml
src/main/java/com/sonyericsson/jenkins/plugins/bfa/BuildFailureScanner.java
src/main/java/com/sonyericsson/jenkins/plugins/bfa/tokens/Token.java
src/test/java/com/sonyericsson/jenkins/plugins/bfa/tokens/TokenTest.java
http://jenkins-ci.org/commit/build-failure-analyzer-plugin/8574f107e801141522b85ab0968d2d0428dddb46
Log:
JENKINS-17658 BUILD_FAILURE_ANALYZER TokenMacro*
Parameters (=default):
includeTitle (=true)
includeIndications (=true)
useHtmlFormat (=false)
Usage:
${BUILD_FAILURE_ANALYZER, includeTitle=true, includeIndications=true, useHtmlFormat=true}
Code changed in jenkins
User: Robert Sandell
Path:
pom.xml
src/main/java/com/sonyericsson/jenkins/plugins/bfa/BuildFailureScanner.java
src/main/java/com/sonyericsson/jenkins/plugins/bfa/sod/ScanOnDemandTask.java
src/main/java/com/sonyericsson/jenkins/plugins/bfa/tokens/Token.java
src/test/java/com/sonyericsson/jenkins/plugins/bfa/tokens/TokenTest.java
http://jenkins-ci.org/commit/build-failure-analyzer-plugin/e9e56046e30fc1b63406d4aeb9eeca81114c574a
Log:
Merge pull request #22 from krwalker/provide-tokenmacro
JENKINS-17658 BUILD_FAILURE_ANALYZER TokenMacro*
Compare: https://github.com/jenkinsci/build-failure-analyzer-plugin/compare/f68d645d86f5...e9e56046e30f
I'd like to see this too. It could quickly help assign who and what remedy may be appropriate.