Skip to content

2.0 (2022-01-31)
Compare
Choose a tag to compare
@avabishchevich avabishchevich released this 01 Feb 15:23
· 236 commits to master since this release
2.0
1df9ebb

Enhancements

  • [#504] Removed mcloud static resource mapping from CE
  • [#494] AWS Marketplace: updated the usage instructions
  • [#493] Bumped up to mcloud 1.8 with Android 12 support
  • [#490] Adjusted Zebrunner Pro intro image using the new trial period

Fixes

Open

  • [#495] AWS Marketplace: start zebrunner CE automatically right after ec2 launch

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.9 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. Apply permissions hotfix removing mcloud/configuration/stf-proxy/ssl folder which is generated under root in 1.9: 
    ls -la mcloud/configuration/stf-proxy/ssl
sudo rm -rf mcloud/configuration/stf-proxy/ssl
  2. 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.8)
 ... mcloud (2.0)
 ... reporting (1.27)
 ... selenoid (1.5)
 ... 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. Specify ZEBRUNNER_VERSION=1.7 updating manually jenkins/variables.env file and restart jenkins
  2. Re-register every organization using Management_Jobs/registerOrganization using up-to-date reporting url and token
  3. Re-register every repository using updated OrgName/RegisterRepository job
  4. [Optional] Upgrade carina-core upto 7.3.15
Assets 2