Project

Profile

Help

Task #7317

Add remove_lock as a run_test post build action in case of timeout or aborted built

Added by Mark Zaslavskiy almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Timofey Turenko
Category:
jenkins_jobs
Sprint/Milestone:
Start date:
28.07.2016
Due date:
% Done:

0%

Estimated time:
0:30 h
Target branch:
Test scenario:

Installation https://dev.osll.ru/issues/7317#note-5

1. Keeping vagrant lock in case of other task created it

Run
- echo "non-existing-job-1111" >> ~/vagrant_lock
- run run_test
- abort run_test
- wait till run_test and smart_remove_lock finished their work

Expected result:
- smart_remove_lock was executed in te end of run_test build
- ~/vagrant_lock exists
- smart_remove_lock failed

2. Successful remove of a vagrant lock in case of aborting task

- run run_test
- wait till vagrant_lock will be aquired
- abort build

Expected result:
- smart_remove_lock was executed in te end of run_test build
- ~/vagrant_lock does not exist
- smart_remove_lock succed


Description

Trigger remove_lock in case of run_test was killed by timeout or aborted by user.

History

#1 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from New to Active / In progress

#2 Updated by Mark Zaslavskiy almost 5 years ago

  • Estimated time set to 0:30 h

#3 Updated by Mark Zaslavskiy almost 5 years ago

DEtremine which "Trigger when build is" value is suitable for case when build should be triggered only in case of aborted.

Do not work
- Stable or unstable but not failed
- unstable or failed but not stable
- unstable

#4 Updated by Mark Zaslavskiy almost 5 years ago

Solution - write on each lock tage.
echo $JOB_NAME-$BUILD_NUMBER >> ~/vagrant_lock

#5 Updated by Mark Zaslavskiy almost 5 years ago

Installation:
1. Merge and pull https://github.com/mariadb-corporation/build-scripts-vagrant/pull/7
2. Merge https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/30
3. Update run_test.yaml and smart_remove_lock.yaml

#6 Updated by Mark Zaslavskiy almost 5 years ago

  • Test scenario updated (diff)

#7 Updated by Mark Zaslavskiy almost 5 years ago

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

#8 Updated by Timofey Turenko almost 5 years ago

  • Status changed from Testing to Closed

Also available in: Atom PDF