diff options
author | sterni <sternenseemann@systemli.org> | 2022-02-06T12·07+0100 |
---|---|---|
committer | sterni <sternenseemann@systemli.org> | 2022-11-04T22·06+0000 |
commit | bf18e657190e6f1c6fa0d5969b6efc45a3599258 (patch) | |
tree | 98e76fddfb72dca59d3c3fd3bc97cde5e0b63fc6 /ops/journaldriver | |
parent | ffec3c70f4d40636b2880681963c83a8ab8853e9 (diff) |
refactor(rust-crates-advisory): redo the buildkite report in bash r/5247
I've elected to split the check-all-our-lock-files script into two new scripts: One very simple script which generates the report by invoking lock-file-report on the fake lock file for //third_party/rust-crates and all lock files in depot, and one which executes this and adds it as a buildkite annotation if there are any warnings (which is reported by the report generating script using a non zero exit code). The latter script could become the basis for generalizing buildkite annotations, a slight attempt at making it easily reusable in the future has been made. So far we expect a report generating script to exit non zero if a report should be made and to print commonmark to stdout. In the future we may want to use a JSON format for generating the report, allowing us to filter it by buildkite target (using the drvmap to exclude certain reports, potentially). Change-Id: I1df9e440509d69adff5b8e6304105a45dc62c018 Reviewed-on: https://cl.tvl.fyi/c/depot/+/5260 Reviewed-by: kn <klemens@posteo.de> Reviewed-by: tazjin <tazjin@tvl.su> Tested-by: BuildkiteCI
Diffstat (limited to 'ops/journaldriver')
0 files changed, 0 insertions, 0 deletions