Project

Profile

Help

Task #7576

remove_lock do not work after create_env abort

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

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

0%

Estimated time:
Target branch:
Test scenario:

http://max-tst-01.mariadb.com:8089/view/All/job/validate_yaml_by_pushes/69/

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

Manual check

Run http://maxscale-jenkins.mariadb.com:8090/job/7576_create_env/

Abort it after a few seconds.

Check that was triggerred

http://maxscale-jenkins.mariadb.com:8090/job/smart_remove_lock/

and

http://maxscale-jenkins.mariadb.com:8090/job/7576_destroy/


Description

еще не сработал remove lock после оборванной create_env

Add smart_remove_lock call as a publisher step

- !include: './maxscale_jobs/include/call_cleanup.yaml'

History

#1 Updated by Mark Zaslavskiy over 4 years ago

  • Assignee changed from Mark Zaslavskiy to Ilfat Kinyaev

#2 Updated by Mark Zaslavskiy over 4 years ago

  • Description updated (diff)
  • Assignee changed from Ilfat Kinyaev to Alexander Kaluzhny

#3 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from New to Active / In progress

#4 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy
  • Test scenario updated (diff)

#5 Updated by Mark Zaslavskiy over 4 years ago

  • Assignee changed from Mark Zaslavskiy to Ilfat Kinyaev

#6 Updated by Ilfat Kinyaev over 4 years ago

  • Assignee changed from Ilfat Kinyaev to Mark Zaslavskiy

#7 Updated by Mark Zaslavskiy over 4 years ago

  • Assignee changed from Mark Zaslavskiy to Ilfat Kinyaev

#8 Updated by Ilfat Kinyaev over 4 years ago

  • Status changed from Review to New
  • Assignee changed from Ilfat Kinyaev to Alexander Kaluzhny

Need to expand test : run modified job with aborted and fails scanarios and check that cleanup is called.

#9 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from New to Active / In progress

#10 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy
  • Test scenario updated (diff)

#11 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Review to New
  • Assignee changed from Mark Zaslavskiy to Alexander Kaluzhny

1. Please use
- !include: './maxscale_jobs/include/call_cleanup.yaml'
insead of https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/78/files#diff-fcf1d6acd100a5ee5c08c7bfa9304354R41

2. Ensure that all params needed for './maxscale_jobs/include/call_cleanup.yaml' are defined. If something is not defined - create copy of './maxscale_jobs/include/call_cleanup.yaml' with different name and hardcoded params values.

#12 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from New to Active / In progress

#13 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy
  • Test scenario updated (diff)

#14 Updated by Mark Zaslavskiy over 4 years ago

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

#15 Updated by Timofey Turenko over 4 years ago

  • Status changed from Testing to Closed

Also available in: Atom PDF