Project

Profile

Help

Task #7375

Prevent running of two run_test_snapshot on the one config

Added by Mark Zaslavskiy over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
High
Assignee:
Timofey Turenko
Category:
mdbci features
Sprint/Milestone:
Start date:
11.08.2016
Due date:
% Done:

0%

Estimated time:
2:00 h
Target branch:
Test scenario:

https://github.com/mariadb-corporation/build-scripts-vagrant/pull/15

https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/47/files

1. Execute run_test snapshot.
2. Fail or abort build/

Expected result - smart_remove_lock_snapshot should be executed.

Aborted build example http://maxscale-jenkins.mariadb.com:8090/view/All/job/run_test_snapshot/1/console

Failed build example: http://maxscale-jenkins.mariadb.com:8090/view/All/job/run_test_snapshot/2/console


Description

- Modify test/run_test_snapshot.sh with
-- lock setting in file $name/snapshot_lock = $JOB_NAME-$BUILD_ID + waiting (use vagrant_lock as an exampe)
-- lock removing in the end of script
- Add job for removing this lock maxscale_jobs/smart_remove_snapshot_lock.yaml (use maxscale_jobs/smart_remove_lock.yaml )
- Add smart_remove_snapshot_lock.yaml call as a postbuild step

History

#1 Updated by Mark Zaslavskiy over 4 years ago

  • Assignee changed from Mark Zaslavskiy to Alexander Kaluzhny

#2 Updated by Mark Zaslavskiy over 4 years ago

  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#3 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from New to Active / In progress

#4 Updated by Mark Zaslavskiy over 4 years ago

How to understand does any snapshot exist for the given config?

#5 Updated by Mark Zaslavskiy over 4 years ago

  • Test scenario updated (diff)

Needed changes in yaml/scripts were made, task require testing - updating create snapshot at maxscale-jenkins and trying to create snapshot for
7375k_snapshot1 (does not have snapshot)
7375k_snapshot (has snapshot)

#6 Updated by Mark Zaslavskiy over 4 years ago

  • Test scenario updated (diff)

#7 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Active / In progress to Review

#8 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Review to Testing
  • Assignee changed from Mark Zaslavskiy to Timofey Turenko

#9 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Testing to Active / In progress
  • Assignee changed from Timofey Turenko to Mark Zaslavskiy

#10 Updated by Mark Zaslavskiy over 4 years ago

  • Subject changed from Prevent second snapshot creation for config to Prevent running of two run_test_snapshot on the one config
  • Description updated (diff)
  • Test scenario updated (diff)

#11 Updated by Mark Zaslavskiy over 4 years ago

  • Description updated (diff)

#12 Updated by Mark Zaslavskiy over 4 years ago

  • Estimated time set to 2:00 h

#13 Updated by Mark Zaslavskiy over 4 years ago

https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/47/files

Added all needed jobs.
Steps to be done:
- modify run_test_snapshot.sh
- validate jobs
- test jobs

#14 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Active / In progress to Testing
  • Assignee changed from Mark Zaslavskiy to Timofey Turenko
  • Test scenario updated (diff)
Installation:
  1. Merge pull-requests
  2. Update build-scripts-vagrant local directory
  3. Create following jobs: maxscale_jobs/remove_lock_snapshot.yaml, maxscale_jobs/smart_remove_lock_snapshot.yaml
  4. Update run_test_snapshot

#15 Updated by Timofey Turenko over 4 years ago

  • Status changed from Testing to Closed

Also available in: Atom PDF