Skip to content

Release Management

Christian Zirkelbach edited this page Dec 20, 2019 · 14 revisions

Release Management

This article describes the Release Management employed in our project. Creating releases, artifacts, and docker images is explained in the following.

Note: The release version 1.5.0 is used as an example

1. Creating a Release on Github

  1. Create a Pull Request (PR) (Branch dev-1 -> master) in the related Repository for the upcoming release.
  2. Merge the PR, if the automatically started Continuous Integration run is successful.
  3. Draft a Release based on the (merged) master branch of the related repository with a release version tag, e.g., 1.5.0, the name, e.g., 1.5.0 (stable), and a corresponding description.

2. Pushing a Release to Dockerhub

2.1 ExplorViz Frontend

2.1.1 Building the artifact

  1. git clone
  2. git checkout 1.5.0
  3. npm install
  4. ember build --prod

2.1.2 Build and push the docker image

  1. export DOCKER_PW=xxx
  2. export DOCKER_LOGIN=xxx
  3. echo "$DOCKER_PW" | docker login -u "$DOCKER_LOGIN" --password-stdin
  4. docker build -t explorviz/explorviz-frontend .
  5. docker tag explorviz/explorviz-frontend:latest explorviz/explorviz-frontend:1.5.0
  6. docker push explorviz/explorviz-frontend

2.2 ExplorViz Backend

2.2.1 Building the artifacts

  1. git clone
  2. git checkout 1.5.0
  3. ./gradlew assemble

2.2.2 Build and push the docker image (needed for every subdirectory (*-service))

  1. cd explorviz-backend-$DIRECTORY
  2. docker build -t explorviz/explorviz-backend-$DIRECTORY .
  3. docker tag explorviz/explorviz-backend-$DIRECTORY:latest explorviz/explorviz-backend-$DIRECTORY:1.5.0
  4. docker push explorviz/explorviz-backend-$DIRECTORY

3. Create new Docker-Compose Setup

Create a new docker-compose file based on the new release-versions in docker-configuration

You can’t perform that action at this time.