[Devops] Need to add UPGRADE_FUEL_TO export to Upgrade jobs

[Andrey Sledzinskiy]

We need to add export UPGRADE_FUEL_TO= to all our upgrade system tests jobs

[Igor Shishkin (teran)]

I'd prefer we add it as a job parameter but hardcoded value with export.

[Dennis Dmitriev (ddmitriev)]

There are three ways how to get the version:

1) For each job, extract the product version from filename of ISO or UPGRADE_TARBALL , as it was done in the bug https://bugs.launchpad.net/fuel/+bug/1382550 for variable UPGRADE_FUEL_TO. It is an easy but not good way because it depends on filename structure that may be changed.

2) The PRODUCT_VERSION for the current branch can be taken from the file https://github.com/stackforge/fuel-main/blob/master/config.mk , as it is done in the job http://jenkins-product.srt.mirantis.net:8080/job/fuel_5_1_iso/ . But the current 'fuel-main' branch never guess which ISO version passed to the test, which may lead to a mismatch.

3) In the parent jobs of system tests (http://jenkins-product.srt.mirantis.net:8080/job/*.system_test.timer ), extract from artifacts not only magnet links, but also 'release' number that can be extracted from ./artifact/version.yaml.txt file and easily exported as environment variables for all downstream jobs.

I beleive the third method is the most appropriate way to get the PRODUCT_VERSION of the ISO passing to the system tests.