[ 
https://issues.apache.org/jira/browse/CASSANDRA-15875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134854#comment-17134854
 ] 

Michael Semb Wever edited comment on CASSANDRA-15875 at 6/13/20, 6:00 PM:
--------------------------------------------------------------------------

Patches:
- 
[trunk|https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_15875]
- 
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/cassandra-3.11_15875]
- 
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/cassandra-3.0_15875]
- 
[2.2|https://github.com/apache/cassandra/compare/cassandra-2.2...thelastpickle:mck/cassandra-2.2_15875]




was (Author: michaelsembwever):
Trunk patch here: 
https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/jenkinsfile-fixes-2020-05

(I will backport these to 2.2, 3.0, 3.11)

> Jenkins pipeline small fixes: slack notification body, 
> StabilityTestDataPublisher, archive cassandra-test-report.txt
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-15875
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15875
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 4.0-beta
>
>
> 1) The slack notification bodies contain an array of SHA commit messages 
> involved in the build. The array needs to be formatting.
> See https://the-asf.slack.com/archives/CS6CA748J/p1592029643136500
> 2) Remove cassandra-builds directory in Summary stage, so 'Restart from 
> Stage' builds work. If the pipeline gets into the final Summary stage it will 
> clone the cassandra-builds directory. Once this happens it is not possible to 
> restart the pipeline. Restarting from a given stage is useful if one of the 
> test stages failed for unknown/infrastructure reasons.
> 3) Archive the cassandra-test-report.txt artifact. This plaintext report was 
> added under CASSANDRA-15729. It should also be made easily available as a 
> downloadable artefact on the build.
> 4) Add StabilityTestDataPublisher to the pipeline junit results. This 
> provides the flakey info next to each test on the test results page. The 
> individual test stages had this enabled, but not the pipeline. For example 
> here: 
> https://github.com/apache/cassandra-builds/blob/master/jenkins-dsl/cassandra_job_dsl_seed.groovy#L252



--
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

Reply via email to