Dawid Weiss created LUCENE-9598:
-----------------------------------
Summary: Improve the summary of Jenkins emails on failure
Key: LUCENE-9598
URL: https://issues.apache.org/jira/browse/LUCENE-9598
Project: Lucene - Core
Issue Type: Improvement
Reporter: Dawid Weiss
Where are the patterns that drive what's extracted from the console logs sent
to builds mailing list? I think these could be improved to include more context
starting after "FAILURE" - then you know which task failed exactly, not just
that the build failed.
{code}
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':solr:solr-ref-guide:checkLocalJavadocLinksSite'.
> Process 'command '/usr/local/asfpackages/java/jdk-11.0.6/bin/java'' finished
> with non-zero exit value 255
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See
https://docs.gradle.org/6.6.1/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 1h 6m 1s
852 actionable tasks: 852 executed
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
[Email-ext] Notification email body length: 446
Sending email to: bui...@lucene.apache.org
Finished: FAILURE
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
