commit | f7e9d86c7f9d89fb973f619edd12e86081954a28 | [log] [tgz] |
---|---|---|
author | Michael Shuler <michael@pbandjelly.org> | Wed May 17 07:11:56 2017 -0500 |
committer | Michael Shuler <michael@pbandjelly.org> | Wed May 17 07:11:56 2017 -0500 |
tree | 70ea2e21ddb9494d0c9cbc232a2537c9ee220f1c | |
parent | f3fdb2bd94b0128a90fabec6809d7397fa9df8b5 [diff] |
Allow concurrent builds on devbranch jobs
jenkins-dsl/
build-scripts/
cassandra-release/
docker/
docker build -f docker/jessie-image.docker docker/
docker build -f docker/centos7-image.docker docker/
The image will contain a clone of the Apache git repository by default. Using a different repository is possible by adding the --build-arg CASSANDRA_GIT_URL=https://github.com/myuser/cassandra.git
parameter. All successive builds will be executed based on the repository cloned during docker image creation.docker run --rm -v `pwd`/dist:/dist `docker images -f label=org.cassandra.buildenv=jessie -q` /home/build/build-debs.sh <branch/tag>
docker run --rm -v `pwd`/dist:/dist `docker images -f label=org.cassandra.buildenv=centos -q` /home/build/build-rpms.sh <branch/tag>
You should find newly created Debian and RPM packages in the dist
directory.
Packages for official releases can only be build from tags. In this case, the tag must match the known versioning scheme. A number of sanity checks will be run to make sure the version matches any version defined in build.xml
and debian/changes
. But you'll have to manually keep these values in sync for every release.
Builds based on any branch will use the version defined in either build.xml
(RPM) or debian/changes
(deb). Afterwards a snapshot indicator will be appended.
TODO