As discovered in canonical/jubilant#301, if a scheduled workflow fails, the person who last modified the schedule (or originally created it, if no modifications) is notified. This is not a very resilient or team-focused solution.
Let's update our scheduled workflows to have an explicit failure notification mechanism (creating an issue with gh is likely simplest):
- example charm integration tests
- integration tests
- published charms tests - maybe not this one, because it regularly fails, although we have made progress, or maybe we can have a set of expected failures or something similar?
- smoke test - currently failing on 2.9, but let's get that fixed
- TIOBE reporting
- updating the best practice doc
- updating the charm test pinning
Please also check there aren't new scheduled workflows when doing this issue. Also, check if there are any in other Charm Tech repos that would also benefit from similar changes.
As discovered in canonical/jubilant#301, if a scheduled workflow fails, the person who last modified the schedule (or originally created it, if no modifications) is notified. This is not a very resilient or team-focused solution.
Let's update our scheduled workflows to have an explicit failure notification mechanism (creating an issue with
ghis likely simplest):Please also check there aren't new scheduled workflows when doing this issue. Also, check if there are any in other Charm Tech repos that would also benefit from similar changes.