runbot/runbot_merge/security/security.xml

<odoo>
    <record model="res.groups" id="group_admin">
        <field name="name">Mergebot Administrator</field>
    </record>
    <record model="res.groups" id="base.group_system">
        <field name="implied_ids" eval="[(4, ref('runbot_merge.group_admin'))]"/>
    </record>
    <record model="res.groups" id="status">
        <field name="name">Mergebot Status Sender</field>
    </record>
</odoo>
[FIX] runbot_merge: work with admin[uid=2] * correctly fetch the admin's uid when running remote tests * looks like I had forgotten to add any sort of access rights, so add some 2018-08-27 20:28:22 +07:00			`<odoo>`
			`<record model="res.groups" id="group_admin">`
			`<field name="name">Mergebot Administrator</field>`
			`</record>`
			`<record model="res.groups" id="base.group_system">`
			`<field name="implied_ids" eval="[(4, ref('runbot_merge.group_admin'))]"/>`
			`</record>`
[ADD] runbot_merge: support for non-webhook staging validation Add support for the ability to validate stagings over RPC rather than via webhook. This may later be expanded to PRs as well. The core motivation for this is to avoid bouncing through github which sometimes drops the ball on statuses, and it's frustrating to have a staging time out because GH fucked up. Implemented via RPC, requiring both the staging itself (by id) and the head commit being affected, as that is necessary to know what CIs are required for that head and correctly report cross branch on the various PRs. Fix #881 (kinda) 2024-06-03 17:59:24 +07:00			`<record model="res.groups" id="status">`
			`<field name="name">Mergebot Status Sender</field>`
			`</record>`
[FIX] runbot_merge: work with admin[uid=2] * correctly fetch the admin's uid when running remote tests * looks like I had forgotten to add any sort of access rights, so add some 2018-08-27 20:28:22 +07:00			`</odoo>`