Skip to content

1.9 (2021-10-26)

Compare
Choose a tag to compare
@avabishchevich avabishchevich released this 26 Oct 20:29
· 287 commits to master since this release
893ee29

Enhancements

  • Made all sub-components individually configured to support multi-hosts and clusterized deployments
  • Improved setup and startup process including non default port and SSL configuration ([#483][#480][#478][#477][#476][#475])

    Make sure to replace self-signed localhost key and certificate in ./nginx/ssl folder with production ready versions!

  • Upgraded all sub-components to the latest versions including reporting, mcloud, jenkins and selenoid
  • Removed basic auth protection for embedded mcloud and selenoid because 99% deployments are inside private VPC ([#482][#481])
  • Documentation review and updates ([#479][#474])

Fixes

  • N/A

Known Issues

  • N/A

Components Updates

Migration Steps

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

Current steps describe migration from 1.8 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
  1. start services and make sure everything is up&running!
./zebrunner.sh start
  1. pull recursively latest changes and verify that sub-modules are valid
git pull --recurse-submodules
  1. Important! Verify that submodules have below versions:
git submodule status
 ... jenkins (1.7)
 ... mcloud (1.7)
 ... reporting (1.26 or 1.26.2)
 ... selenoid (1.4)
 ... sonarqube (1.3)

There is no sense to continue if any sub-module has older version! Ask for the assistance in telegram

  1. run "upgrade" task
./zebrunner.sh upgrade
// Answer "y" to start an upgrade and restart services.
  1. Login to jenkins and upgrade SSH Server plugin to 3.1.0
    • Manage Jenkins -> Manage Plugins -> Updates
    • Pick SSH Server to be upgraded to 3.1.0+

    Without manual upgrade of this plugin Jenkins stack on dependencies error on plugins!

  2. Restart Jenkins
  3. Make sure to upgrade carina-core upto 7.2.12!
  4. [Optional] If you use your AWS S3 bucket as a storage, 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/