Zebrunner is a Test Automation Management Tool
Note: It is possible to migrate from 1.0+ versions automatically!
Current steps describe migration from 1.4 release.
./zebrunner.sh backup
cp -r ../zebrunner ../zebrunner.bak
./zebrunner.sh start
git pull --recurse-submodules
git submodule status
... jenkins (1.4-4-g74f61db)
... mcloud (1.4)
... reporting (1.20)
... selenoid (1.2-2-g6d64b13)
... sonarqube (1.2-2-gcd35598)
There is no sense to continue if any sub-module has older version! Ask for the assistance in telegram
./zebrunner.sh upgrade
// Answer "y" to start an upgrade and restart services.
cd zebrunner
aws s3 cp reporting/minio-storage/configuration/minio/data/templates/test_run_results.ftl s3://your-bucket/templates/
Note: It is possible to migrate from 1.0+ versions automatically!
Current steps describe migration from 1.3 release.
./zebrunner.sh backup
cp -r ../zebrunner ../zebrunner.bak
./zebrunner.sh start
git pull --recurse-submodules
git submodule status
... jenkins (1.4)
... mcloud (1.3)
... reporting (1.19)
... selenoid (1.2)
... sonarqube (1.2)
There is no sense to continue if any sub-module has older version! Ask for the assistance in telegram
./zebrunner.sh upgrade
// Answer "y" to start an upgrade and restart services.
For MCloud upgrade one extra question should appear:
Do you want to remove MCloud FTP data volume? You might lose old video recordings!-> Answer "n" to keep FTP artifacts.
@Library('[email protected]')
->
@Library('[email protected]')
with 6.5.46 and lower versions video recording will be corrupted
aws-jacoco-token jenkins credsNote: It is possible to migrate from 1.0, 1.1 and 1.2 versions automatically!
Current steps describe migration from 1.2 release.
./zebrunner.sh backup
cp -r ../zebrunner ../zebrunner.bak
./zebrunner.sh start
git pull --recurse-submodules
git submodule status
... jenkins (1.3)
... mcloud (1.2)
... reporting (1.16)
... selenoid (1.1-2-g8a510df)
... sonarqube (1.2)
There is no sense to continue if any sub-module has older version! Ask for the assistance in telegram
./zebrunner.sh upgrade
// Answer "y" to start an upgrade and restart services.
Note: It is possible to migrate from 1.0 and/or 1.1 versions automatically!
./zebrunner.sh backup
cp -r ../zebrunner ../zebrunner.bak
./zebrunner.sh start
git pull --recurse-submodules
git submodule status
... jenkins (1.2-4-gd9ea800)
... mcloud (1.2)
... reporting (1.14)
... selenoid (1.1-2-g8a510df)
... sonarqube (1.2)
There is no sense to continue if any sub-module has older version! Ask for the assistance in telegram
./zebrunner.sh upgrade
// Answer "y" to start an upgrade, provide "n" replies if you don't use custom pipeline libraries and global choices and restart services.
S3_ENDPOINT=https://s3.us-east-1.amazonaws.com:443
S3_ACCESS_KEY_ID=<access_key>
S3_SECRET=<secret_key>
S3_REGION=us-east-1
S3_BUCKET=mybucket
./zebrunner.sh upgrade For details, take a look at Migration Steps./zebrunner.sh backup
cp -r ../zebrunner ../zebrunner.bak
./zebrunner.sh start
git pull --recurse-submodules
git submodule status
... jenkins (1.1)
... mcloud (3.3)
... reporting (1.12.1)
... selenoid (remotes/origin/master)
... sonarqube (1.1)
There is no sense to continue if any sub-module has older version!
./zebrunner.sh upgrade
// answer "y" to make an upgrade and restart services
docker rm -f stf-auth-mock
Starting from now it is called "Zebrunner Community Edition".
Next 1-2 releases we are going to release both versions for each organization
./zebrunner setup
./zebrunner.sh start
./zebrunner.sh stop
./zebrunner.sh restart
./zebrunner.sh down
./zebrunner.sh shutdown
That's a valid steps for upgrading from 5.1 and 5.2 releases! Please, ask asistance if you wanna to upgrade from 4.x version
docker exec -it jenkins-master /bin/bash
rm -rf ./var/jenkins_home/init.groovy.d/*
ls -la ./var/jenkins_home/init.groovy.d
edit .env file with new tag
git clone --recurse-submodule https://github.com/zebrunner/zebrunner.git
cd zebrunner
./zebrunner.sh setup
make sure to provide the same credentials you have in your previous environment
cd qps-infra/selenoid
./update.sh
// two latest versions of chrome, firefox and opera browsers should be downloaded
// restart infra
TAG_JENKINS_MASTER=5.1
TAG_SONAR=2.2
TAG_STF=3.2
name: gc_PIPELINE_LIBRARY
value: QPS-Pipeline
name: gc_RUNNER_CLASS
values:
com.qaprosoft.jenkins.pipeline.runner.maven.TestNG
com.qaprosoft.jenkins.pipeline.runner.maven.Runner
com.qaprosoft.jenkins.pipeline.runner.gradle.Runner
Due to the full folders redesign it is recommended to clone to absolutely fresh folder and move historical data from previous version based on steps below:
Deploy a new infra tool set from scratch according to the steps and start. Do a sanity verification that all enabled components are up&running
Migrate historical jenkins data:
volumes:
- "/home/ubuntu/old-qps-infra/jenkins:/var/jenkins_home"
# - "data-volume:/var/jenkins_home:rw"
Migrate historical Zafira data:
volumes:
- "/home/ubuntu/old-qps-infra/pgdata:/var/lib/postgresql/data"
# - "pgdata-volume:/var/lib/postgresql/data"
- "./database/:/docker-entrypoint-initdb.d"
volumes:
- "/home/ubuntu/old-qps-infra/pgdata:/usr/share/elasticsearch/data"
# - "esdata-volume:/usr/share/elasticsearch/data"
- "./configuration/elasticsearch/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml:ro"
zafira 4.1.73->4.1.90 zafira-ui 1.25->1.38 jenkins-master 4.9.1->4.10.2 qps-pipeline 4.9->4.10.2
./stop.sh
cd qps-infra
tar -czvf jenkins.tar.gz ./jenkins
sudo tar -czvf pgdata.tar.gz ./pgdata
docker rmi <id>
volumes:
- $PWD/selenoid/video:/usr/share/ftp:rw
Bump up images in docker-compose.yml
Start everything
./start.sh
// stop infra and keep containers
./stop.sh -k
zafira 4.1.73->4.1.89 zafira-ui 1.25->1.35 jenkins-master 4.8->4.9.1 qps-pipeline 4.8->4.9.1
./stop.sh
cd qps-infra
tar -czvf jenkins.tar.gz ./jenkins
sudo tar -czvf pgdata.tar.gz ./pgdata
./start.sh