[
https://issues.apache.org/jira/browse/CASSANDRA-16377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280815#comment-17280815
]
Michael Semb Wever commented on CASSANDRA-16377:
------------------------------------------------
bq. Do we have runs with changes linked somewhere?
I will commit the cassandra-builds patch first and post a run of it.
bq. It would be nice to have a helper method for running similar stages instead
of copying the code
Absolutely. But… the tentative plan is to bring all the stage jobs over from
cassandra_job_dsl_seed.groovy, writing them directly into the Jenkinsfiles.
This will remove the need for a separate devbranch jenkinsfile, and also bring
over the build-scripts (which we can then hopefully change the circleci to use
as well). I was thinking of just doing it one stage job at a time, e.g.
starting with artifacts. In that process hopefully we can find ways to make the
code less boilerplate.
> Add dtest-upgrade and dtest-large-novnode to Jenkins pipeline
> -------------------------------------------------------------
>
> Key: CASSANDRA-16377
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16377
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Low
> Fix For: 3.0.x, 3.11.x, 4.0.x
>
>
> Now that dtest-upgrade test runs are passing they can be considered for
> addition to the jenkins pipeline. And dtest-large-novnode only as one failure
> so should be added too.
> https://the-asf.slack.com/archives/CK23JSY2K/p1610132643162700
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
