1.5 (2021-02-16)

Enhancements

• [#405] Added information about templates updates for AWS S3 storage use-case
• [#397] Added the default minio setup if user disable AWS S3 integration

Fixes

• [#406][#392] Shutdown procedure should remove all ".disabled" files
• [#403] Mail service doesn't work. Failed to process message MailDataMessage

Known Issues

• [#2243][#409] AWS S3 Templates sync up needed
  Apply workarounds manually for AWS S3 templates based on the tickets

Components Updates

• reporting 1.19 -> 1.20
• mcloud 1.3 -> 1.4 (mcloud-grid 1.0 -> 1.1)

Migration Steps

Note: It is possible to migrate from 1.0+ versions automatically!

Current steps describe migration from 1.4 release.

1. it is recommended to make a "golden" backup running backup task and making a copy of zebrunner folder

./zebrunner.sh backup
cp -r ../zebrunner ../zebrunner.bak

2. start services and make sure everything is up&running!

./zebrunner.sh start

3. pull recursively latest changes and verify that sub-modules are valid

git pull --recurse-submodules

4. Important! Verify that submodules have below versions:

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

5. run "upgrade" task

./zebrunner.sh upgrade
// Answer "y" to start an upgrade and restart services.

6. [Optional] If you use your AWS S3 bucket, please, upload manually new minio test_run_results.ftl template into the s3://your-bucket/templates/

cd zebrunner
aws s3 cp reporting/minio-storage/configuration/minio/data/templates/test_run_results.ftl s3://your-bucket/templates/