[
https://issues.apache.org/jira/browse/CASSANDRA-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169897#comment-17169897
]
Michael Semb Wever commented on CASSANDRA-15925:
------------------------------------------------
bq. Why are stage failures not being reported now? They used to appear before
the final total report.
Nice spot! Yes, there's some muffins there they way pipelines, blue ocean, and
unstable builds are visualised.
A little bit of background to this is in blog post:
https://www.jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/
I might be wrong, but I believe with the patch we are at "as good as it gets"
with the current Jenkins API and plugins.
> Jenkins pipeline can copy wrong test report artefacts from stage builds
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-15925
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15925
> Project: Cassandra
> Issue Type: Bug
> Components: CI
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0-rc
>
>
> Spotted in
> https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/196/console
> Looks like copyArtifact will need to be specific to a build.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
