2.0 (2022-01-31)
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
- [#501] 400 error after opening https://demo.zebrunner.farm
- [#499] Unable to source utility.sh when launch zebrunner.sh from different folder
Open
- [#495] AWS Marketplace: start zebrunner CE automatically right after ec2 launch
Known Issues
- N/A
Components Updates
- reporting 1.26 -> 1.27
- mcloud 1.7 -> 2.0
- selenoid 1.4 -> 1.5
- jenkins 1.7->1.8
- pipeline-ce 1.6->1.7
Migration Steps
Note: It is possible to migrate from 1.0+ versions automatically!
Current steps describe migration from 1.9 release.
- 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
- start services and make sure everything is up&running!
./zebrunner.sh start
- Apply permissions hotfix removing
mcloud/configuration/stf-proxy/ssl
folder which is generated underroot
in 1.9:ls -la mcloud/configuration/stf-proxy/ssl sudo rm -rf mcloud/configuration/stf-proxy/ssl
- pull recursively latest changes and verify that sub-modules are valid
git pull --recurse-submodules
- 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
- run "upgrade" task
./zebrunner.sh upgrade
// Answer "y" to start an upgrade and restart services.
- Specify
ZEBRUNNER_VERSION=1.7
updating manuallyjenkins/variables.env
file and restart jenkins - Re-register every organization using
Management_Jobs/registerOrganization
using up-to-date reporting url and token - Re-register every repository using updated
OrgName/RegisterRepository
job - [Optional] Upgrade carina-core upto 7.3.15