Skip to content

1.8 (2021-06-29)
Compare
Choose a tag to compare
@avabishchevich avabishchevich released this 29 Jun 12:51
· 378 commits to master since this release
1.8
275fe74
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Enhancements

  • [#274][#451] Important! Support of launchers, github integrations via UI and project labels dropped in 1.8!
  • Dropped support of ldap integration (SAML based authentication might be requested instead)
  • [#434][#445][#456][#458][#464] Bump up to reporting 1.24
  • [#445][#447][#463] Bump up to jenkins-master 1.5
  • [#395] Bump up to jenkins-slave to 1.2

Fixes

  • N/A

Known Issues

  • #26 Can't attach files with new update 
    Apply workaround manually updating selenoid/docker-compose.yml removing "$ENABLE_FILE_UPLOAD" argument.
    For details visit: zebrunner/selenoid#27

Components Updates

Migration Steps

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

Current steps describe migration from 1.7 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.5)
 ... mcloud (1.6-7-ga4937a8)
 ... reporting (1.24)
 ... selenoid (1.3-6-ga7777bf)
 ... sonarqube (1.2-3-gedee3cf)

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. enable error message hash codes recalculation appending reporting/configuration/reporting-service/variables.env file with:
RECALCULATE_HASH_CODE_TASK_ENABLED=true
RECALCULATE_HASH_CODE_TASK_DB_QUERY_BATCH_SIZE=200
RECALCULATE_HASH_CODE_TASK_REINDEXING_DELAY=1s
  1. restart reporting-service
docker rm -f reporting-service
./zebrunner.sh start
  1. look into the reporting-service logs to see:
Trying to acquire redis lock by key recalculate-test-hashes-based-on-first-200-char ...
Lock was successfully acquired.
Start hashes recalculation
Downstream hashes recalculation started.
Downstream hashes recalculation finished.
Upstream hashes recalculation started.
Upstream hashes recalculation finished.
End hashes recalculation
Statistics: {...}
  1. Disable recalculation RECALCULATE_HASH_CODE_TASK_ENABLED=false and restart reporting
docker rm -f reporting-service
./zebrunner.sh start

[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/
Assets 2
Loading