Knowing who triggered a deployment is useful in a number of scenarios. For example, when a scheduled deployment fails due to the previous deployment being a partial deployment, the team is notified thus:
The View partial deploy link goes to the deployment log page; knowing who did this partial deployment makes it easier to triage.
All deployment options
- [Deploy build 3417 of `tools::riffraff` to CODE](https://riffraff.gutools.co.uk/deployment/deployAgain?project=tools%3A%3Ariffraff&build=3417&stage=CODE&updateStrategy=MostlyHarmless&action=deploy)
- [Deploy parts of build 3417 to CODE by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=tools%3A%3Ariffraff&build=3417&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
3 weeks ago
What does this change?
Add the name of who started a deployment on log page. To make it easier to parse the amount of information, tabulate the data.
Before
After (when deployed to CODE)
How can we measure success?
Knowing who triggered a deployment is useful in a number of scenarios. For example, when a scheduled deployment fails due to the previous deployment being a partial deployment, the team is notified thus:
The
View partial deploylink goes to the deployment log page; knowing who did this partial deployment makes it easier to triage.