fvp_utils: include the test configuration info as LAVA metadata
Usually LAVA jobs are found starting from Jenkins jobs, i.e. L1 ->
gateway -> builder, then the latter triggering/storing the LAVA job
log. However Jenkins' build-discarter policy removes Jenkins
jobs (jobs are no longer available at original URLs) at some point,
leaving the LAVA job the only available CI job from the original
pipeline.
This patch introduces test configuration as metadata, which is the
information that uniquely identifies how the artefacts are compiled
and tested by LAVA, allowing it to easily (re)trigger jobs from Jenkins.
Signed-off-by: Leonardo Sandoval <leonardo.sandoval@linaro.org>
Change-Id: If545ca0848267f9f45dad684b49b45bccfdc620d
diff --git a/script/gen_fvp_linux_yaml.sh b/script/gen_fvp_linux_yaml.sh
index e209978..cbd8d72 100755
--- a/script/gen_fvp_linux_yaml.sh
+++ b/script/gen_fvp_linux_yaml.sh
@@ -10,6 +10,9 @@
# to correct values
cat <<EOF
+metadata:
+ test_config: {TEST_CONFIG}
+
device_type: fvp
job_name: fvp-linux-{MODEL}
diff --git a/script/gen_fvp_tftf_yaml.sh b/script/gen_fvp_tftf_yaml.sh
index 9af659a..caf1d0a 100755
--- a/script/gen_fvp_tftf_yaml.sh
+++ b/script/gen_fvp_tftf_yaml.sh
@@ -10,6 +10,9 @@
# to correct values
cat <<EOF
+metadata:
+ test_config: {TEST_CONFIG}
+
device_type: fvp
job_name: fvp-tftf-{MODEL}