Avoid hardcoding branches for plugins: use variables
To eliminate manual repo_name/branch_name setting for plugin Jenkins
jobs, let's use variables 'reponame' and 'branchname' for plugin
templates instead (as we do in system tests).
+ it's better having YAML sections divided by empty lines to improve
readability.
Reviewed: https:/ /review. fuel-infra. org/19635
Submitter: Aleksandra Fedorova <email address hidden>
Branch: master
Commit: fbb134556ac55d8 38441da8d79ff17 a279446cbc
Author: Lesya Novaselskaya <email address hidden>
Date: Thu Apr 14 12:29:21 2016
Avoid hardcoding branches for plugins: use variables
To eliminate manual repo_name/ branch_ name setting for plugin Jenkins
jobs, let's use variables 'reponame' and 'branchname' for plugin
templates instead (as we do in system tests).
+ it's better having YAML sections divided by empty lines to improve
readability.
Closes-Bug: #1540365
Change-Id: I6673c94c8ec34e 49b77e9fa8c754c 765ac293849
Signed-off-by: Lesya Novaselskaya <email address hidden>