[
https://issues.apache.org/jira/browse/CASSANDRA-18249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686694#comment-17686694
]
Michael Semb Wever commented on CASSANDRA-18249:
------------------------------------------------
bq. I think keeping the existing build system and adding a package building
step to releasing is the most attractive solution of these, not to mention the
simplest, and I'll start putting that together.
I think I've done something like this already in CASSANDRA-18133
(ref:
https://github.com/michaelsembwever/cassandra/commit/fee6dbd452740b43500268b9b339956a023961fa
)
Then, it's just the deb and rpm repo stuff that also need to be dockerised.
> Docker image for releases
> -------------------------
>
> Key: CASSANDRA-18249
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18249
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Berenguer Blasi
> Assignee: Brandon Williams
> Priority: Normal
>
> The release process is currently driven bu this
> [doc|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/release_process.adoc]
> mainly.
> Some of the requirements are a Debian based distro and a number of packages.
> As recently discovered this could be a problem, Ubuntu 20.04 LTS doesn't have
> createrepo available i.e.
> To avoid such problems, add repeatability, have a controlled env where
> releases are cut, enable more people to cut them, etc [~mck] suggested
> creating a docker image to that purpose probably based off
> [this|https://github.com/apache/cassandra-builds/blob/trunk/docker/bullseye-image.docker]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
