tree: af37d086ba98ab8563c862ab64335de68a8865a9 [path history] [tgz]
  1. .gitignore
  2. Dockerfile
  5. release_manager.profile

Release Helper Scripts

A full guide to releases can be found on confluence. In addition, you'll need to understand key signing and publish a PGP key using your apache email. PGP key generation is discussed here.

Non managers can use the script to run a test of the release artifacts.

Preq's For Script Usage

You must fill out release_manager.profile first.

You'll need these tools:

  • md5sum
  • shasum
  • svn
  • gpg
  • tar
  • gzip

This is of course in addition to the regular build tools.

Script Overview

For non-release managers

# Test a candidate
# You will run this if you are a non-release manager testing a release.
./ test

For release managers

# Create candidate artifacts
# (did you set the .profile file?)
./ create

# Publish candidate artifacts
# (did you first create and test the release artifacts?)
./ publish


We‘ve included a Dockerfile which can be used as a platform standard for testing. That is, many of us develop on Mac, so it’s convenient to be able to test on Ubuntu without leaving your machine. This is for purely for convenience. You can test on any supported platform.

Basic docker usage is shown below.

# cd to release directory

# build the image from the Dockerfile
docker build -t quickstep-dev .

# enter a fresh docker container
docker run -ti quickstep-dev bash

# now you are in the container. Here you can clone quickstep and run the release scripts for testing