You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
CI is currently not archiving all logs that are needed to analyze failures. E.g. in #10647 (comment) I am missing integration-tests/maven/target/test-classes/projects/multimodule-resources-classpath/build-multimodule-resources-classpath.log.
This is especially obstructive when flaky tests are involved and/or your local operating system differs from CI.
Implementation ideas
I propose to create for each build/job an archive (or add to the existing one) with all logfiles under target (however deeply nested).
Furthermore I propose to archive **/target/surefire-reports/* and **/target/failsafe-reports/*. Not sure about Gradle, though.
Description
CI is currently not archiving all logs that are needed to analyze failures. E.g. in #10647 (comment) I am missing
integration-tests/maven/target/test-classes/projects/multimodule-resources-classpath/build-multimodule-resources-classpath.log
.This is especially obstructive when flaky tests are involved and/or your local operating system differs from CI.
Implementation ideas
I propose to create for each build/job an archive (or add to the existing one) with all logfiles under
target
(however deeply nested).Furthermore I propose to archive
**/target/surefire-reports/*
and**/target/failsafe-reports/*
. Not sure about Gradle, though.I also propose the set
trimStackTrace
tofalse
for the entire repo.See also: https://lists.apache.org/thread.html/r9030808273c82ac6d7b9602d34d446c7d8c4e8aa02c41bca164df1c5%40%3Cdev.maven.apache.org%3E (meaning that even the Maven maintainers suggest to disable it)
The text was updated successfully, but these errors were encountered: