https://validation.linaro.org/static/docs/v2/standard-test-jobs.html#job-met... The above link destripes how to define metadata in job. But how to use these metadata defines?
On Wed, 19 Sep 2018 at 12:02, chao yang yangchao.free@gmail.com wrote:
https://validation.linaro.org/static/docs/v2/standard-test-jobs.html#job-met... The above link destripes how to define metadata in job. But how to use these metadata defines?
Store data about this particular test job. Metadata consists of a key and a value, both are simple strings.
Use metadata to describe the state of your CI at the moment the test job was submitted. Latest git commit hash for the source code used in the build. What branch is being used, is there a useful tag relating to the source code at this point? What was the URL of the script used to make the build? Is there a useful README file alongside the builds that could help someone understand failures in the test job later?
Metadata can also be used in a Query, so that you can pick out test jobs or test cases related to a specific source code change via the commit hash. A Query can use a metadata key as a "named attribute" and can match on the value.
Metadata exists to provide a way to describe the test job without resorting to a never ending, complex, job description.
Use a human friendly job description and put all the search criteria etc. into the metadata.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
lava-users@lists.lavasoftware.org
-
chao yang -
Neil Williams