[ 
https://issues.apache.org/jira/browse/CASSANDRA-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-21629:
-----------------------------------------
    Description: In CASSANDRA-18145 the k8s-based immutable provisioning and 
repeatable CI was added and has enjoyed great success.  It was forward-looking 
and applied to the 5.0 branch and up, but now with a year of hindsight we can 
see there have been eight 4.x releases and these won't stop until 7.0 is 
released.  It would be beneficial to the project to have a unified CI process 
for all branches before that occurs.  (was: In CASSANDRA-18145 the k8s-based 
immutable provisioning and repeatable CI was added and has enjoyed great 
success.  It was forward-looking and applied to the 5.0 branch and up, but now 
with a year of hindsight we can see there have been eight 4.x releases and 
these won't stop until 7.0 releases.  It would be beneficial to the project to 
have a unified CI process for all branches before that occurs.)

> Modernize the 4.x CI pipeline (Backport CASSANDRA-18145)
> --------------------------------------------------------
>
>                 Key: CASSANDRA-21629
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21629
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: CI
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x
>
>
> In CASSANDRA-18145 the k8s-based immutable provisioning and repeatable CI was 
> added and has enjoyed great success.  It was forward-looking and applied to 
> the 5.0 branch and up, but now with a year of hindsight we can see there have 
> been eight 4.x releases and these won't stop until 7.0 is released.  It would 
> be beneficial to the project to have a unified CI process for all branches 
> before that occurs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to