Project

Profile

Help

Task #7898

Restrict available nodes to max-tst02 and maxtst03 at build_and_performance

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

Status:
Closed
Priority:
High
Category:
jenkins_slaves
Sprint/Milestone:
Start date:
11.01.2017
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

http://maxscale-jenkins.mariadb.com:8090/view/All/job/build_and_performance_test/build?delay=0sec

available nodes: max-tst02 and maxtst03

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


Description

Add version of https://github.com/mariadb-corporation/maxscale-jenkins-jobs/pull/117/files#diff-c08fc17317622a2a48d0678dc8974853 without master in allowed-nodes to build_and_performance_test yaml

History

#1 Updated by Mark Zaslavskiy almost 5 years ago

  • Subject changed from Restrict available to max-tst02 and maxtst03 at build_and_performance to Restrict available nodes to max-tst02 and maxtst03 at build_and_performance

#2 Updated by Tatyana Berlenko almost 5 years ago

  • Status changed from New to Active / In progress

#3 Updated by Tatyana Berlenko almost 5 years ago

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

#4 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Review to New
  • Assignee changed from Mark Zaslavskiy to Tatyana Berlenko

Please make separate clone of slave.yaml without master specified and restore slave.yaml back - it is already used in several other jobs.

#5 Updated by Timofey Turenko almost 5 years ago

I suggest just to change default node from master to maxtst3 and do not remove any node from the list. 'master' can be selected manually and can not be used automatically.

#6 Updated by Timofey Turenko almost 5 years ago

  • Status changed from New to Closed

maxtst3 is default now

Also available in: Atom PDF