Skip to content

Draft: [LOW PRIORITY; but interesting to me at least] Use a bot to automate backporting bugs

John Skarbekrequested to merge
jts/automate-bug-fixes into master

What does this MR do and why?

  • Look for all issues in the current milestone with a merged MR
  • Ask someone if we can help them, by auto backporting to the current set of stable branches
  • Do just that
  • Via a rake task that we'd schedule to run on occasion, we'll sniff out issues that match our criterion, ping users, perform cherry-picks, and merge MR's

This would be similar to our security policy by having a bot assist users and performing merges, but this operates strictly on bugs. The bot is slightly interactive in requesting confirmation from the person and noting that they remain responsible. Proper error handling is intended such that if something fails along the way we are notified. The ultimate goal with this is, if accepted, make it work, as there are flaws at this current moment, and maybe remove our pilot program in favor of automation.

Note

99% of this code was written by Duo Though I do wish I knew the actual percentage because I did at least touch some of this manually as Duo was being a pain in the butt.

Warning

This does not work in its current form

  • Logic around state needs to be redone. The code as written will forget it's managing an MR the next time the Raketask runs
  • The logic around WHO we reach out to needs to be thought about. Currently it'll ping the issue author which is likely not what we want.
  • The logic for message checking would need to be redone as it suffers the same problem for state tracking.

I figure I'd at least get a process written even if not working just to see how far I can stretch Duo.

Author Check-list

  • Has documentation been updated?
Edited by John Skarbek

Merge request reports