utils: use different artifacts for tfa-next on fvp
As the tfa-next jobs are private, so are their generated binaries.
The Open CI infrastructure is not designed to support running the
FVP tests with private binaries.
Because of this, said binaries will be uploaded to a public S3
bucket.
* Change job.yaml so that fvp-next jobs run the FVP with the files
uploaded to that public S3 bucket instead of using the artifacts
generated by the private job.
* Identify each binary with the date and time they were created at
so that:
a) They are differentiated from other binaries.
b) They can be removed by a separate "cleanup" job after they've
been there for a specific period of time (to be determined by
that job).
.) The uploading of the files to the S3 bucket will be done by the
builder job on tf-a-job-configs.
.) The cleanup job mentioned above will also be performed by a
script in tf-a-job-configs.
Change-Id: I22e9275d7187f9ac7616a714140b68199c44c84a
Signed-off-by: Tomás González <tomasagustin.gonzalezorlando@arm.com>
diff --git a/utils.sh b/utils.sh
index 2ff56b8..46089da 100644
--- a/utils.sh
+++ b/utils.sh
@@ -190,10 +190,16 @@
# Generate link to an archived binary.
gen_bin_url() {
local bin_mode="${bin_mode:?}"
+ local next_bin="${next_bin:?}"
local bin="${1:?}"
if upon "$jenkins_run"; then
- echo "$jenkins_url/job/$JOB_NAME/$BUILD_NUMBER/artifact/artefacts/$bin_mode/$bin"
+ if upon "$next_bin"; then
+ date_time="$(date +'%Y-%m-%d-%H%M%S')"
+ echo "https://downloads.trustedfirmware.org/tf-a/next/artifacts/$date_time/$bin_mode/$bin"
+ else
+ echo "$jenkins_url/job/$JOB_NAME/$BUILD_NUMBER/artifact/artefacts/$bin_mode/$bin"
+ fi
else
echo "file://$workspace/artefacts/$bin_mode/$bin"
fi