Daily summary of failed scheduled master due to `schedule:package-and-qa`
As @kwiebers highlighted in our 1:1, it looks that schedule:package-and-qa
is contributing to the number of failed scheduled pipelines.
For the time being I think we should separate these two pipelines by allowing the schedule:package-and-qa
job to fail, and address the gitlab-qa
pipeline success rate (the second chart) independently.
This way, at least we avoid the bystander effect where other developers may start to ignore broken master in #development
. They can focus on broken master that may be due to other reasons.
To maintain awareness on the failing schedule:package-and-qa
, we could have a daily summary posted as an issue, where it lists the failed pipelines and the downstream gitlab-qa
job.
/cc @gl-quality/eng-prod what do you think?
Edited by Albert Salim