We want to enforce a relation between repository and project (at least). As a pre-requisite, this change adds some structured logging on each successful parsing of the build.json files. We can these use these logs to understand which projects, if any, might be impacted by the aforementioned restriction.
All deployment options
- [Deploy build 3293 of `tools::riffraff` to CODE](https://riffraff.gutools.co.uk/deployment/deployAgain?project=tools%3A%3Ariffraff&build=3293&stage=CODE&updateStrategy=MostlyHarmless&action=deploy)
- [Deploy parts of build 3293 to CODE by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=tools%3A%3Ariffraff&build=3293&stage=CODE&updateStrategy=MostlyHarmless)
- [What's on CODE right now?](https://riffraff.gutools.co.uk/deployment/history?projectName=tools%3A%3Ariffraff&stage=CODE)
github-actions[bot]
commented
4 months ago
What does this change?
We want to enforce a relation between repository and project (at least). As a pre-requisite, this change adds some structured logging on each successful parsing of the
build.jsonfiles. We can these use these logs to understand which projects, if any, might be impacted by the aforementioned restriction.How to test
Deploy to CODE, and observe the logs.