tree 5b84ee61d74a774a9ff3ecb276518ab3bb5dfa93
parent e72d538d2810c53436e6e5593795d25086ee04ca
author Tomás González <tomasagustin.gonzalezorlando@arm.com> 1737131540 +0000
committer Tomás González <tomasagustin.gonzalezorlando@arm.com> 1739353607 +0000

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>