Releasing

As prerequisites to release:

• The release branch (e.g. maint-0.7 for bug fixes or master for new versions) has to:
  • Have a release commit as last commit
  • Have a tag pointing to the last commit
  • Pass the reana-dev run-ci test in production mode

Python packages

1. Release the package(s)

$ reana-dev release-pypi -c reana-db

Docker images

1. Clean your environment

$ cd ~/mysrc/reana-server
$ reana-dev git-clean -c .

2. Build the image(s)

$ reana-dev docker-build -c .

3. Tag and release the image(s)

$ reana-dev git-tag -c .
$ reana-dev release-docker -c .

Helm Charts

1. Upgrade to the latest cluster component versions:

$ reana-dev helm-upgrade-components

2. Create new release tag locally, push release branch to GitHub, and clean your local GitHub Pages branch:

$ reana-dev git-tag -c .
$ git clean -d -ff -x
$ git push upstream master
$ (git checkout gh-pages && git fetch upstream && git reset --hard upstream/gh-pages)

3. Bump the chart version and release it:

$ cr upload --help | grep release-name-template # check whether you have cr>1.0.0 version with --r-n-t flag
$ reana-dev release-helm
$ (git checkout gh-pages && git log -1 -p && git push upstream gh-pages)

The new version will be visible in the REANA Helm repository shortly after.