Fix issues about reusing data when triggering updates
- Sep 04, 2021
-
-
Emanuele Aina authored
The `public/data.yaml` generated by the dashboard contains all the combined data to let triggers do their job, using it gives more flexibility later on. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Emanuele Aina authored
When retrieving an artifacts from a past job with a job token, the `JOB-TOKEN``header should be used rather than the `PRIVATE-HEADER` and the API URL should be used rather than the enduser route. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Emanuele Aina authored
Repeat with me: `test -e` stands for "file exists", *not* for "string is empty", as that's `test -z`. Update the test in `trigger-updates` accordingly to properly print the help text when the variable is not set. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-