[
https://issues.apache.org/jira/browse/CASSANDRA-15838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121342#comment-17121342
]
Michael Semb Wever edited comment on CASSANDRA-15838 at 6/1/20, 9:25 PM:
-------------------------------------------------------------------------
Patch at
https://github.com/apache/cassandra-builds/compare/master...thelastpickle:mck/15838
An offline conversation with [~mshuler] raised the concern about the source
artefacts being rebuilt from scratch from the git sha inside the docker
containers.
Being able to pass in the already built source artefact into the docker
containers, so there is the same original source artefact re-used in both the
deb and rpm packages, is considered a requirement but slated for a later
ticket. The priority in this ticket is to create a more robust (tested)
approach to the deb/rpm packages that we distribute. It's currently too brittle
with the debian patches are only applied and tested when cutting a release, and
not having any "nightlies" of deb/rpm available. Take eg the version.properties
[breakage|CASSANDRA-15830] in the alphas.
To test locally…
{code}cd cassandra
../cassandra-builds/build-scripts/cassandra-artifact.sh
# the "builds/" directory should now contain normal build artefacts as well as
the deb and rpm artefacts
{code}
To test in Jenkins
- set up local jenkins
- run the dsl job from the branch, including the following the env
!Screenshot 2020-06-01 at 12.29.21.png|width=500!
- after a successful build of the `Cassandra-*-artifacts` job, the following
artifacts should be attached
!Screenshot 2020-06-01 at 23.24.39.png|width=500!
To test the release process…
{code}
cd cassandra
../cassandra-builds/cassandra-release/prepare_release.sh -f <version>
{code}
was (Author: michaelsembwever):
Patch at
https://github.com/apache/cassandra-builds/compare/master...thelastpickle:mck/15838
An offline conversation with [~mshuler] raised the concern about the source
artefacts being rebuilt from scratch from the git sha inside the docker
containers.
Being able to pass in the already built source artefact into the docker
containers, so there is the same original source artefact re-used in both the
deb and rpm packages, is considered a requirement but slated for a later
ticket. The priority in this ticket is to create a more robust (tested)
approach to the deb/rpm packages that we distribute. It's currently too brittle
with the debian patches are only applied and tested when cutting a release, and
not having any "nightlies" of deb/rpm available. Take eg the version.properties
[breakage|CASSANDRA-15830] in the alphas.
To test locally…
{code}cd cassandra
../cassandra-builds/build-scripts/cassandra-artifact.sh
# the "builds/" directory should now contain normal build artefacts as well as
the deb and rpm artefacts
{code}
To test in Jenkins
- set up local jenkins
- run the dsl job from the branch, including the following the env
!Screenshot 2020-06-01 at 12.29.21.png|width=500!
- after a successful build of the `Cassandra-*-artifacts` job, the following
artifacts should be attached
To test the release process…
{code}
cd cassandra
../cassandra-builds/cassandra-release/prepare_release.sh -f <version>
{code}
> Add deb and rpm packaging to artifacts test script
> --------------------------------------------------
>
> Key: CASSANDRA-15838
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15838
> Project: Cassandra
> Issue Type: Task
> Components: Build, CI, Packaging
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 4.0-beta
>
> Attachments: Screenshot 2020-06-01 at 12.29.21.png, Screenshot
> 2020-06-01 at 23.24.39.png
>
>
> Currently we have no way of testing debian or rpm packaging. This is a
> problem, it hurts when cutting releases as well as afterwards (like
> CASSANDRA-15830).
> This ticket is to add testing of debian or rpm packaging into the artifacts
> test script.
> This will also provide "nightly" build artifacts for the deb and rpm packages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
