[
https://issues.apache.org/jira/browse/CASSANDRA-17664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-17664:
-------------------------------------------
Fix Version/s: 2.2.20
3.0.28
3.11.14
4.0.5
4.1
4.2
(was: 2.2.x)
(was: 3.0.x)
(was: 4.x)
(was: 3.11.x)
(was: 4.0.x)
(was: 4.1.x)
Source Control Link:
https://github.com/apache/cassandra/commit/136c8c0f65cc8f2db87bb683e6eaceb05016f00e
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as
[136c8c0f65cc8f2db87bb683e6eaceb05016f00e|https://github.com/apache/cassandra/commit/136c8c0f65cc8f2db87bb683e6eaceb05016f00e].
> 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]
