The v3 migration script can handle these just fine - but if we go ahead
and remove them the output can be predominantely shell rather than
script.
Change-Id: I440851a0149e1cc7f8c5c6e8a4e3e0b94088ee82
The two scripts do the same, just have one different parameter. Use a
single script and rename it.
The scripts are included directly in yaml and do not life anymore in the
scripts directory so that changes to them will be directly and don't
need new images to be built.
Change-Id: Ia229b118daabb1f43da1507a37a4fd3724c2512a
We cannot mix code and includes, this needs to be separated.
Use two include commands and split out the initial content to another
file.
Change-Id: I04584e301078cc851ae258525dc1c4b662ed6c28
Pass variables in so that the script can be merged with
jobs/scripts/run-install-guide.sh.
Remove setting of $result, the script is run with bash -xe and therefore
result is never set, the script is aborted earlier.
Change-Id: I0cea5debba63863135b53c5447713a80d989c1a5
Create jenkins/jobs/include directory and move the two scripts that we
currently have into that directory.
Adjust builders using the scripts.
Change-Id: If0cda5a6749dd19fdc57b6f64a6f7ed5ac5bfc00