Project

Profile

Help

Task #7729

configure build and run_test_snapshot to be executed on different slaves

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

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

0%

Estimated time:
Target branch:
Test scenario:

Pul request: https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/99/files

Manual testing.
Go to http://maxscale-jenkins.mariadb.com:8090/search/?q=7729

Each job represents real job but simplified (just runs shell script with 'exit 1') and with added node label (node on wich job will be triggered - maxtst2)

Run both jobs and check that every subjob is triggered on same node (maxtst2)


Description

Add same-node/node-parameters option to other subbuild calls for build and run_test_snapshot (we should check all chain of calls and fix them)

same-node (bool) – Use the same node for the triggered builds that was used for this build (optional)
http://docs.openstack.org/infra/jenkins-job-builder/builders.html#builders.trigger-builds
http://docs.openstack.org/infra/jenkins-job-builder/publishers.html#publishers.trigger-parameterized-builds
node-parameters (bool) – Use the same Node for the triggered builds that was used for this build. (optional)

History

#1 Updated by Mark Zaslavskiy over 4 years ago

  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#2 Updated by Mark Zaslavskiy over 4 years ago

  • Description updated (diff)
  • Assignee changed from Mark Zaslavskiy 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)

Pul request: https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/99/files

Manual testing.
Go to http://maxscale-jenkins.mariadb.com:8090/search/?q=7729

Each job representin real job but without simplified (just runs shell script with 'exit 1') and with added node label (node on wich task will be triggered - maxtst2)

Run bith jobs and check every subjob to be triggered on same node (maxtst2)

#5 Updated by Alexander Kaluzhny over 4 years ago

  • Test scenario updated (diff)

#6 Updated by Alexander Kaluzhny over 4 years ago

  • Test scenario updated (diff)

Pul request: https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/99/files

Manual testing.
Go to http://maxscale-jenkins.mariadb.com:8090/search/?q=7729

Each job represents real job but simplified (just runs shell script with 'exit 1') and with added node label (node on wich job will be triggered - maxtst2)

Run both jobs and check that every subjob is triggered on same node (maxtst2)

#7 Updated by Mark Zaslavskiy over 4 years ago

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

#8 Updated by Alexander Kaluzhny over 4 years ago

To make it all work next jobs must be updated on server:
maxscale_jobs/build.yaml
maxscale_jobs/cleanup.yaml
maxscale_jobs/smart_remove_lock.yaml
maxscale_jobs/run_test_snapshot.yaml
maxscale_jobs/smart_remove_lock_snapshot.yaml

#9 Updated by Timofey Turenko over 4 years ago

  • Status changed from Testing to Closed

Also available in: Atom PDF