1.2 (2020-11-09)
Enhancements
- Bump up Java 8 -> 11 on jenkins-slave
- [#276][#234] Certified integration with github/gitlab and bitbucket repositories
- [#324] Selenium video recording pushed to S3 compatible storage (by default into embedded minio)
- [#319] Automated jenkins upgrade tasks
- [#335][#334][#322][#316] Improved warn/info messages and guide for the next steps like start/restart etc
- [#314][#280] Added support for special symbols except quotas and ambiguous characters
Fixes
- [#336] Backup/restore should not be started for disabled components
- [#331] Fixed the issue when it was impossible to create a new widget
- [#326] Public filters did not work in the Zebrunner UI tool
- [#321] Automatic services startup are not started
- [#264] Updated User Guide .xml file configuration parameters list
Known Issues
- [#347] reporting can't be started after upgrade to 1.2: function update_modified_at() does not exist
- #2243 AWS S3: Providers not available in Test Launchers
Apply workaround manually for AWS S3 templates based on the ticket - Some conflicts might appear for manually installed jenkins plugins. It is recommended to upgrade all compatible to the latest versions in such case.
[COMPONENTS UPDATES]
- reporting 1.12 -> 1.14
- jenkins-master 1.1 -> 1.2
- sonarqube 1.1 -> 1.2
- mcloud 3.3 -> 1.2 (3.4 in qps)
[MIGRATION STEPS]
Note: It is possible to migrate from 1.0 and/or 1.1 versions automatically!
- 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
- 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.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
- run "upgrade" task
./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.
- Login to Jenkins
- Re-register again Organization via Management_Jobs/RegisterOrganization job
Note: hopefully last time when organization should be re-registered :) - Re-register again all your repositories using <ORG_NAME>/RegisterRepository jobs
Note: make sure to provide scmType and repoUrl in new way using https or ssh url! - Obligatory remove in Manage Jenkins -> Configure System GITHUB_* global variables:
- GITHUB_HOST
- GITHUB_API_URL
- GITHUB_ORGANIZATION
- GITHUB_HTML_URL
- GITHUB_OAUTH_TOKEN
- GITHUB_SSH_URL
- [Optional] Remove in Manage Jenkins -> Configure System deprecated global variables:
- QPS_PIPELINE_GIT_BRANCH
- QPS_PIPELINE_GIT_URL
- QPS_PIPELINE_LOG_LEVEL
- In case of using AWS S3 as a storage manually update ./selenoid/.env parameters using valid S3 data for
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