runbot/forwardport/data
Xavier Morel 8a931adeac [IMP] forwardport: better fw batch failure notification
When an fw batch fails, log a message to its chatter (so the reason
for the failure doesn't necessarily have to be hunted down in the
logs, although depending on the quality of the error that might still
be an issue).

Also if a batch keeps failing (fails for more than a day at a retry
every hour -- increased from a previous 30mn), stop retrying it and
flag it in the list view, it's clearly not going to go through.

This is because we hit an issue with a completion fw batch created on
January 27th which kept failing until it was deleted on February
10th. Thankfully it failed on `git push` and git operations apparently
are not rate limited at all, but still it's not great stewartship to
keep trying a forwardport which keeps failing. Retrying in case of
transient failure makes sense, but after 24 attempts over a day it's
either not transient, or it's not working because github is down and
hammering it won't help.
2025-02-13 14:26:50 +01:00
..
crons.xml [IMP] *: trigger-ify task queue type crons 2024-08-02 15:14:50 +02:00
queues.xml [IMP] forwardport: better fw batch failure notification 2025-02-13 14:26:50 +01:00
security.xml [CHG] *: move repo cache from forwardbot to mergebot 2023-08-25 15:04:48 +02:00
views.xml [IMP] forwardport: show a user's outstanding tally in the main alert 2025-01-24 15:54:58 +01:00