[
https://issues.apache.org/jira/browse/CASSANDRA-18133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-18133:
-------------------------------------------
Description:
Bring the artifact/deb/rpm build scripts (and associated docker images) from
cassandra-builds repo to the .build directory.
The declarative Jenkinsfile can then directly declare the artifacts jobs in its
pipeline. And the packaging jobs can be separated and run in parallel.
This addresses the epic's stated existing problems:
- difficult to pre-commit test jenkins and cassandra-build changes,
- CI development efforts is split between ci-cassandra and circleci, despite
ci-cassandra being our canonical and non-commercial CI,
- lacking parity of what is tested between ci-cassandra and circleci
- cassandra-builds as a separate repo (without release branches matching
in-tree) adds complexity to changing matrix values (jdks, pythons, dist)
- mixture of jenkins dsl groovy, declarative and scripting pipeline.
- different pre-commit and post-commit jenkins pipelines are used.
In addition it addresses:
- stage jobs don't always running on the same SHA as the pipeline's run,
- infra issues around networking, specifically git cloning additional
cassandra-builds repository,
- a more readable Jenkinsfile
- more UX friendly build and test scripts
was:
Bring the artifact/deb/rpm build scripts (and associated docker images) from
cassandra-builds repo to the .build directory.
The declarative Jenkinsfile can then directly declare the artifacts jobs in its
pipeline. And the packaging jobs can be separated and run in parallel.
> In-tree build scripts
> ---------------------
>
> Key: CASSANDRA-18133
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18133
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 5.x
>
>
> Bring the artifact/deb/rpm build scripts (and associated docker images) from
> cassandra-builds repo to the .build directory.
> The declarative Jenkinsfile can then directly declare the artifacts jobs in
> its pipeline. And the packaging jobs can be separated and run in parallel.
> This addresses the epic's stated existing problems:
> - difficult to pre-commit test jenkins and cassandra-build changes,
> - CI development efforts is split between ci-cassandra and circleci, despite
> ci-cassandra being our canonical and non-commercial CI,
> - lacking parity of what is tested between ci-cassandra and circleci
> - cassandra-builds as a separate repo (without release branches matching
> in-tree) adds complexity to changing matrix values (jdks, pythons, dist)
> - mixture of jenkins dsl groovy, declarative and scripting pipeline.
> - different pre-commit and post-commit jenkins pipelines are used.
> In addition it addresses:
> - stage jobs don't always running on the same SHA as the pipeline's run,
> - infra issues around networking, specifically git cloning additional
> cassandra-builds repository,
> - a more readable Jenkinsfile
> - more UX friendly build and test scripts
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
