Test Upgrade with Docker
With Docker-Compose
Test upgrade in docker with docker-compose
 |
PTC does not take any responsibility and is not liable for any damage caused through use of this image, be it indirect, special, incidental or consequential damages (including but not limited to damages for loss of business, loss of profits, interruption or the like).
It is highly recommended to create daily backups and keep them for several days. For more information on backups, see: How to create a backup.
|
|
|
The following docker setup is only for evaluation purposes. PTC does not recommend the usage of dockerized databases.
|
|
|
This page requires advanced docker and docker-compose know-how.
|
|
|
Tomcat is unresponsive during the Codebeamer upgrade. Tomcat and the container will only be available once the upgrade is completed successfully.
|
Create volumes
docker volume create codebeamer-db-data && \
docker volume create codebeamer-app-repository-docs && \
docker volume create codebeamer-app-repository-search && \
docker volume create codebeamer-app-logs
Example upgrade from 2.0.0.0 to 2.1.0.0
|
|
For a different version, modify the tag in intland/Codebeamer:<version>.
|
Docker-compose file
Create the docker-compose.yml file with the following content:
version: '2.1'
services:
codebeamer-db:
image: postgres:15
healthcheck:
- test: ["CMD", "pg_isready"]
- interval: 10s
- timeout: 30s
- retries: 5
- start_period: 30s
environment:
- POSTGRES_USER=user
- POSTGRES_PASSWORD=pass
- POSTGRES_DB=codebeamer
- TZ=Europe/Berlin
volumes:
- codebeamer-db-data:/var/lib/postgresql/data
codebeamer-app:
image: intland/codebeamer-git:2.1.0.0
- depends_on:
- codebeamer-db:
- condition: service_healthy
environment:
- CB_CONTEXT_PATH=cb
- CB_REDIRECT_TO=localhost:8080/cb
- TZ=Europe/Berlin
- WAIT_HOSTS=codebeamer-db:5432
- WAIT_HOSTS_TIMEOUT=1
- CB_database_JDBC_Username=user
- CB_database_JDBC_Password=pass
- CB_database_JDBC_Driver=org.postgresql.Driver
- CB_database_JDBC_ConnectionURL=jdbc:postgresql://codebeamer-db:5432/codebeamer?autoReconnect=true&zeroDateTimeBehavior=convertToNull&emulateLocators=true&characterEncoding=UTF-8&useSSL=false
- CB_database_JDBC_Timeout=120
- CB_mail_localname=localhost
- CB_mail_serverScheme=https
- CB_mail_serverPort=8443
- volumes:
- codebeamer-app-repository-docs:/home/appuser/codebeamer/repository/docs
- codebeamer-app-repository-search:/home/appuser/codebeamer/repository/search
- codebeamer-app-logs:/home/appuser/codebeamer/logs
- links:
- codebeamer-db:container-mysql
volumes:
- codebeamer-db-data:
- name: codebeamer-db-data
- external: true
- codebeamer-app-repository-docs:
- name: codebeamer-app-repository-docs
- external: true
- codebeamer-app-repository-search:
- name: codebeamer-app-repository-search
- external: true
- codebeamer-app-logs:
- name: codebeamer-app-logs
- external: true
Go to the directory containing the previously created docker-compose.yml file, and run the following command:
docker-compose up
The logs will be visible.
Alternatively, it can be started in the background with the following command:
docker-compose up -d
Run Codebeamer at http://localhost:8080, and perform the following steps:
• Create a new project.
• Create a new git repository.
• Upload a document.
Stop Codebeamer
In case Codebeamer was started without the -d command, press ctrl +c.
In case Codebeamer was started with the -d command, run the following line in the directory containing the docker-compose.yml:
docker-compose down
Start Codebeamer
Change the version in the below line of the docker-compose.yml file:
image: intland/codebeamer-git:9.3.0 --> image: intland/codebeamer:9.4.0
Then, run the following command in the directory containing the docker-compose.yml:
docker-compose up
The logs will be visible.
Alternatively, it can be started in in the background with the following command:
docker-compose up -d
The update is successful if the below criteria are met:
• No exceptions in the log.
• Previously created project, repository found and works in the new container (9.4.0 in the example).
• Uploaded document is available in the new container (9.4.0 in the example).