5
0
mirror of https://github.com/odoo/runbot.git synced 2025-03-21 10:25:44 +07:00
runbot/forwardport/models/forwardport.py
Xavier Morel f671dcc828 [ADD] forwardbot
* Cherrypicking is handrolled because there seems to be no easy way to
  programmatically edit commit messages during the cherrypicking
  sequence: `-n` basically squashes all commits and `-e` invokes a
  subprocess. `-e` with `VISUAL=false` kinda sorta works (in that it
  interrupts the process before each commit), however there doesn't
  seem to be clean status codes so it's difficult to know if the
  cherrypick failed or if it's just waiting for a commit of this step.

  Instead, cherrypick commits individually then edit / rewrite their
  commit messages:

  * add a reference to the original commit
  * convert signed-off-by to something else as the original commit was
    signed off but not necessarily this one

* Can't assign users when creating PRs: only repository collaborators
  or people who commented on the issue / PR (which we're in the
  process of creating) can be assigned.

  PR authors are as likely to be collaborators as not, and we can have
  non-collaborator reviewers. So pinging via a regular comment seems
  less fraught as a way to notify users.
2019-09-05 10:00:07 +02:00

92 lines
3.3 KiB
Python

# -*- coding: utf-8 -*-
import logging
from contextlib import ExitStack
import subprocess
from odoo import fields, models
_logger = logging.getLogger(__name__)
class Queue:
def _process_item(self):
raise NotImplementedError
def _process(self):
while True:
b = self.search([], limit=1)
if not b:
return
b._process_item()
b.unlink()
self.env.cr.commit()
class BatchQueue(models.Model, Queue):
_name = 'forwardport.batches'
_description = 'batches which got merged and are candidates for forward-porting'
batch_id = fields.Many2one('runbot_merge.batch', required=True)
source = fields.Selection([
('merge', 'Merge'),
('fp', 'Forward Port Followup'),
], required=True)
def _process_item(self):
batch = self.batch_id
# only some prs of the batch have a parent, that's weird
with_parent = batch.prs.filtered(lambda p: p.parent_id)
if with_parent and with_parent != batch.prs:
_logger.warn("Found a subset of batch %s (%s) with parents: %s, should probably investigate (normally either they're all parented or none are)", batch, batch.prs, with_parent)
newbatch = batch.prs._port_forward()
if newbatch:
_logger.info(
"Processing %s (from %s): %s (%s) -> %s (%s)",
self.id, self.source,
batch, batch.prs,
newbatch, newbatch.prs,
)
else: # reached end of seq (or batch is empty)
# FIXME: or configuration is fucky so doesn't want to FP (maybe should error and retry?)
_logger.info(
"Processing %s (from %s): %s (%s) -> end of the sequence",
self.id, self.source,
batch, batch.prs
)
batch.active = False
class UpdateQueue(models.Model, Queue):
_name = 'forwardport.updates'
_description = 'if a forward-port PR gets updated & has followups (cherrypick succeeded) the followups need to be updated as well'
original_root = fields.Many2one('runbot_merge.pull_requests')
new_root = fields.Many2one('runbot_merge.pull_requests')
def _process_item(self):
previous = self.new_root
with ExitStack() as s:
for child in self.new_root._iter_descendants():
# QUESTION: update PR to draft if there are conflicts?
_, working_copy = previous._create_fp_branch(
child.target, child.refname, s)
new_head = working_copy.stdout().rev_parse(child.refname).stdout.decode().strip()
# update child's head to the head we're going to push
child.with_context(ignore_head_update=True).head = new_head
working_copy.push('-f', 'target', child.refname)
# committing here means github could technically trigger its
# webhook before sending a response, but committing before
# would mean we can update the PR in database but fail to
# update on github, which is probably worse?
# alternatively we can commit, push, and rollback if the push
# fails
# FIXME: handle failures (especially on non-first update)
self.env.cr.commit()
previous = child