Project

Profile

Help

Task #7944

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

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

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

0%

Estimated time:
Target branch:
Test scenario:

All slaves (maxtst2 and maxtst3) are test VMs on maxscale-jenkins server

Testing for build associated jobs:
run http://maxscale-jenkins.mariadb.com:8090/job/7944_daily_build_all/, it will trigger http://maxscale-jenkins.mariadb.com:8090/job/7944_build_all/ on the same node (maxtst2), it will trigger two configurations: centos_7_libvirt and centos_6_libvirt. They will trigger http://maxscale-jenkins.mariadb.com:8090/job/7944_build/ on same node (maxtst2).

*Note for using NODE_NAME environmental variable: here http://maxscale-jenkins.mariadb.com:8090/job/7944_build_all/2/injectedEnvVars/ we can see this variable is set to maxtst2 (which is what we need BUT using $slave_name works two), same thing for http://maxscale-jenkins.mariadb.com:8090/job/7944_build/1/injectedEnvVars/. So here https://github.com/mariadb-corporation/maxscale-jenkins-jobs/blob/14c28574ca39ec2560fa6d33a4644b10e8c0efae/maxscale_jobs/include/call_remove_lock.yaml#L6 and https://github.com/mariadb-corporation/maxscale-jenkins-jobs/blob/14c28574ca39ec2560fa6d33a4644b10e8c0efae/maxscale_jobs/include/call_destroy.yaml#L12 we can also use slave_name=$NODE_NAME

Review comment: https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/130#pullrequestreview-20167027

Testing jobs are here: http://maxscale-jenkins.mariadb.com:8090/job/7944_build_all/search/?q=7944


Description

Pay attention to slave_name=$slave_name . May be they should be changed to slave_name=${NODE_NAME}

History

#1 Updated by Mark Zaslavskiy almost 5 years ago

  • Category set to jenkins_slaves
  • Assignee set to Alexander Kaluzhny
  • Priority changed from Normal to High
  • Sprint/Milestone set to 0.9

#2 Updated by Alexander Kaluzhny almost 5 years ago

  • Status changed from New to Active / In progress

#3 Updated by Alexander Kaluzhny almost 5 years ago

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

All slaves (maxtst2 and maxtst3) are test VMs on maxscale-jenkins server

Testing for build associated jobs:
run http://maxscale-jenkins.mariadb.com:8090/job/7944_daily_build_all/, it will trigger http://maxscale-jenkins.mariadb.com:8090/job/7944_build_all/ on the same node (maxtst2), it will trigger two configurations: centos_7_libvirt and centos_6_libvirt. They will trigger http://maxscale-jenkins.mariadb.com:8090/job/7944_build/ on same node (maxtst2).

*Note for using NODE_NAME environmental variable: here we can see this variable is set to maxtst2 (which is what we need BUT using $slave_name works too), same thing for http://maxscale-jenkins.mariadb.com:8090/job/7944_build/1/injectedEnvVars/. So here https://github.com/mariadb-corporation/maxscale-jenkins-jobs/blob/14c28574ca39ec2560fa6d33a4644b10e8c0efae/maxscale_jobs/include/call_remove_lock.yaml#L6 and https://github.com/mariadb-corporation/maxscale-jenkins-jobs/blob/14c28574ca39ec2560fa6d33a4644b10e8c0efae/maxscale_jobs/include/call_destroy.yaml#L12 we can also use slave_name=$NODE_NAME

Review comment: https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/130#pullrequestreview-20167027

#4 Updated by Alexander Kaluzhny almost 5 years ago

  • Test scenario updated (diff)

All slaves (maxtst2 and maxtst3) are test VMs on maxscale-jenkins server

Testing for build associated jobs:
run http://maxscale-jenkins.mariadb.com:8090/job/7944_daily_build_all/, it will trigger http://maxscale-jenkins.mariadb.com:8090/job/7944_build_all/ on the same node (maxtst2), it will trigger two configurations: centos_7_libvirt and centos_6_libvirt. They will trigger http://maxscale-jenkins.mariadb.com:8090/job/7944_build/ on same node (maxtst2).

*Note for using NODE_NAME environmental variable: here http://maxscale-jenkins.mariadb.com:8090/job/7944_build_all/2/injectedEnvVars/ we can see this variable is set to maxtst2 (which is what we need BUT using $slave_name works two), same thing for http://maxscale-jenkins.mariadb.com:8090/job/7944_build/1/injectedEnvVars/. So here https://github.com/mariadb-corporation/maxscale-jenkins-jobs/blob/14c28574ca39ec2560fa6d33a4644b10e8c0efae/maxscale_jobs/include/call_remove_lock.yaml#L6 and https://github.com/mariadb-corporation/maxscale-jenkins-jobs/blob/14c28574ca39ec2560fa6d33a4644b10e8c0efae/maxscale_jobs/include/call_destroy.yaml#L12 we can also use slave_name=$NODE_NAME

Review comment: https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/130#pullrequestreview-20167027

Testing jobs are here: http://maxscale-jenkins.mariadb.com:8090/job/7944_build_all/search/?q=7944

#5 Updated by Alexander Kaluzhny almost 5 years ago

  • Test scenario updated (diff)

#6 Updated by Alexander Kaluzhny almost 5 years ago

  • Test scenario updated (diff)

#7 Updated by Alexander Kaluzhny almost 5 years ago

  • Test scenario updated (diff)

#8 Updated by Mark Zaslavskiy almost 5 years ago

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

#9 Updated by Timofey Turenko almost 5 years ago

  • Status changed from New to Closed

Also available in: Atom PDF