[infra][ci] Swarm threads for testing plugins are using 'master' branch instead of 'stable/x'

[Vladimir Khlyunev]

https://product-ci.infra.mirantis.net/view/8.0_swarm/job/8.0.system_test.ubuntu.plugins.fuel_plugin_example/configure
'Branches to build - origin/master'

We have to reconfigure all 8.0 jobs for using stable/8.0 branch of fuel-qa repository.

[Alexandr Kostrikov (akostrikov-mirantis)]

Correct branch for mitaka:
https://product-ci.infra.mirantis.net/view/9.0_swarm/job/9.0.system_test.ubuntu.error_node_reinstallation/76/console
 > git rev-parse refs/remotes/origin/stable/mitaka^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/stable/mitaka^{commit} # timeout=10

Affected jobs:
https://product-ci.infra.mirantis.net/view/9.0_swarm/job/9.0.system_test.ubuntu.plugins.thread_keystone_separate_services/76/console
https://product-ci.infra.mirantis.net/view/9.0_swarm/job/9.0.system_test.ubuntu.plugins.thread_db_separate_services/76/console
https://product-ci.infra.mirantis.net/view/9.0_swarm/job/9.0.system_test.ubuntu.plugins.thread_2_separate_services/76/console
https://product-ci.infra.mirantis.net/view/9.0_swarm/job/9.0.system_test.ubuntu.plugins.fuel_plugin_example/76/console

[Vasily Gorin (vgorin)]

I have just found some reasons Why it doesn't work correct.
1. We specify git repository directly in plugin-template.yaml. In other cases repository is specified directly in jobs and after that it is used in template by them name.
2. plugin-template uses openstack macros as scm while system_tests template uses maingit.
3. For main git we should specify repobranch as 'stable/mitaka'(prefix 'origin' is specified inside macros) while for maingit we specify as 'origin/stable/mitaka'

first point is that we should take reponame and repobranch for plugins-template from the job specification.
Second point is that we should have the same format of naming for different scm macros.

Connect with me for questions.

[Vasily Gorin (vgorin)]

Correct typo :
3. For openstack macros we should specify repobranch as 'stable/mitaka'(prefix 'origin' is specified inside macros) while for maingit we specify as 'origin/stable/mitaka'

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: master
Change author: Lesya Novaselskaya <email address hidden>
Review: https://review.fuel-infra.org/19635

[Lesya Novaselskaya (onovaselskaya)]

review: https://review.fuel-infra.org/#/c/19635/

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/19635
Submitter: Aleksandra Fedorova <email address hidden>
Branch: master

Commit: fbb134556ac55d838441da8d79ff17a279446cbc
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: I6673c94c8ec34e49b77e9fa8c754c765ac293849
Signed-off-by: Lesya Novaselskaya <email address hidden>