Skip to content

1.4 (2021-01-25)

Compare
Choose a tag to compare
@avabishchevich avabishchevich released this 25 Jan 12:35
· 509 commits to master since this release
738204c

Enhancements

  • [#381][#353] Simplified setup process removing 8 questions and making reporting an obligatory component
  • [#382] Enabled an easy way to manage Live VNC sessions including custom ones
  • [#378] Configured external S3 storage for mcloud and selenoid if reporting is disabled
  • [#352][#268] Improved default README documentation steps
  • [#371] Limited nginx logs by size (512Mb)
  • [#351] Disabled 3rd party integration with browserstack/saucelabs, etc.
  • [#329] Setup tools order in case of disabled reporting
  • [#291] provided sample skeleton and default folders for SSL setup on NGiNX

Fixes

  • [#383] Don't put to NOTICE.txt information about empty integrations
  • [#376] Reviewed and updated references to selenium-hub container name using mcloud-grid
  • [#268] Zebrunner doc contained out-of-date image of structure

Known Issues

  • #2243 AWS S3: Providers not available in Test Launchers
    Apply workaround manually for AWS S3 templates based on the ticket

Components Updates

Migration Steps

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

Current steps describe migration from 1.3 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.4)
 ... mcloud (1.3)
 ... reporting (1.19)
 ... selenoid (1.2)
 ... sonarqube (1.2)

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.

For MCloud upgrade one extra question should appear:
Do you want to remove MCloud FTP data volume? You might lose old video recordings!
-> Answer "n" to keep FTP artifacts.

  1. Login to Jenkins, edit <your_organization>/RegisterRepository job(s) updating pipeline library version:
@Library('[email protected]')
->
@Library('[email protected]')
  1. Reregister all your test repositories using updated above RegisterRepository job(s).
    Important! To be in sync with reporting changes minimal carina-core versions are 6.5.47 and 7.0.0

with 6.5.46 and lower versions video recording will be corrupted

  1. [Optional] Remove aws-jacoco-token jenkins creds