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

Michael Semb Wever commented on CASSANDRA-17664:
------------------------------------------------

New in-tree patches:
 - 
[2.2|https://github.com/apache/cassandra/compare/cassandra-2.2...thelastpickle:mck/17664-take2/2.2]
 - 
[3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...thelastpickle:mck/17664-take2/3.0]
 - 
[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...thelastpickle:mck/17664-take2/3.11]
 - 
[4.0|https://github.com/apache/cassandra/compare/cassandra-4.0...thelastpickle:mck/17664-take2/4.0]
 - 
[4.1|https://github.com/apache/cassandra/compare/cassandra-4.1...thelastpickle:mck/17664-take2/4.1]
 - 
[trunk|https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/17664-take2/trunk]

> Retry failed stage jobs in jenkins
> ----------------------------------
>
>                 Key: CASSANDRA-17664
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17664
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CI
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 2.2.20, 3.0.28, 3.11.14, 4.0.5, 4.1, 4.2
>
>
> To avoid failing pipeline builds on CI infrastructure faults (disks, network, 
> etc), retry stage jobs three times before marking them as FAILURE.
> Intention is not to retry on UNSTABLE (tests failing).
> This has already been done (and tested) for devbranch pipeline (pre-commit) 
> [here|https://github.com/apache/cassandra-builds/pull/72].



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to