Make a branch stable/8.0 for fuel plugins repository

[Alexander Kurenyshev]

We need a branch stable/8.0 for fuel plugins repository [0].
This mean that after branch creation we should update plugin builder jobs for SWARM 8.0 to make it possible clone stable branch instead of master.

Also we need to update all plugins repositories such as detach-keystone [1] and specify correct links for downloading plugins at jobs that it using

[0] https://github.com/openstack/fuel-plugins
[1] https://github.com/openstack/fuel-plugin-detach-keystone

[Dmitry Kaigarodеsev (dkaiharodsev)]

related patchset for branching: https://review.openstack.org/#/c/275780/

[Ihor Kalnytskyi (ikalnytskyi)]

> We need a branch stable/8.0 for fuel plugins repository [0].

Why do you need so? Please explain what are you trying to achieve, and then let's decide what we need and how to do it.

Because Fuel Plugin Builder is untied from Fuel release cycle, and Fuel versioning. It has own release cycle and own versioning scheme. We usually release it after Fuel HCF, and before Fuel release.

[Alexander Kurenyshev (akurenyshev)]

Igor, I absolutely agree with you. We need a tag instead of a branch at repo fuel-plugins. At the detached plugin repo we need a branch, I think

[Dmitry Kaigarodеsev (dkaiharodsev)]

@Igor, Alexander let me propose to you alternative way for now (without tagging or brunching):

- to use specified commit of 'fuel-plugins' repository for 8.0 jobs

and patchset with such solution is on review here:
https://review.fuel-infra.org/#/c/16125/

as you can see on line 33 (https://review.fuel-infra.org/#/c/16125/18/servers/jenkins-product-ci/8.0/build-fuel-plugins.yaml)
I propose to use current latest commit and it can be changed by request (or by bug)

[Aleksandra Fedorova (bookwar)]

We created stable/8.0 branch in detach-database, detache-rabbitmq and detach-keystone plugins used in swarm threads:

https://github.com/fuel-infra/jenkins-jobs/blob/master/common/plugins-template.yaml#L14-L16

So this bug is no blocked only by decision on versioning of the fuel-plugin-builder itself.

There are options

1) use master branch of fuel-plugins
2) use hardcoded git sha of current HEAD of fuel-plugins repo
3) create new tag in fuel-plugins repo and stick to it (should be confirmed with @ikalnitsky)

QA team, please decide on which option to use.

[Alexander Kurenyshev (akurenyshev)]

Since the Fuel Plugin Builder should be able to create and build plugins of all and any versions, we decided to use master.

Tests for the Fuel 8.0 that use example plugins from a fpb repo shouldn't be updated. They still will download built plugins (with master FPB) and install it at Fuel 8.0.

The same tests for the Fuel 9.0 should be reworked (the new path to the built plugin 5.0.0 should be defined) to use 5.0.0 version which is only supported by the Fuel 9.0. The job which builds plugin shouldn't be updated in case that there should be new example plugin v.5.0.0 at the fuel-plugins repo, and that job will build this plugin too. Should be implemented after this bug will be released https://bugs.launchpad.net/fuel/+bug/1534126

Tests which build plugins inside containers for Fuel 8.0 should use a `--package-version 4.0.0` argument when a plugin template is created. The same tests for Fuel 9.0 shouldn't use this argument and this will tests template creating for plugins. https://bugs.launchpad.net/fuel/+bug/1549399

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

Change abandoned by Dmitry Kaigarodsev <email address hidden> on branch: master
Review: https://review.fuel-infra.org/16125
Reason: https://bugs.launchpad.net/fuel/+bug/1534124