NextERP/runbot
5
0
Fork 0
mirror of https://github.com/odoo/runbot.git synced 2025-03-15 23:45:44 +07:00
Code Issues Actions Packages Projects Releases Wiki Activity
18.0
runbot/runbot_merge/security/security.xml

24 lines
787 B
XML
Raw Permalink Normal View History

[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>
[ADD] runbot_merge: support for unstaged patches Unstaged changes can be useful or necessary for some tasks e.g. absolute emergency (where even faking the state of a staging is not really desirable, if that's even possible anymore), or changes which are so broad they're difficult to stage (e.g. t10s updates). Add a new object which serves as a queue for patch to direct-apply, with support for either text patches (udiff style out of git show or format-patch) or commits to cherry-pick. In the former case, the part of the show / format-patch before the diff itself is used for the commit metadata (author, committer, dates, message) whereas for the commit version the commit itself is reused as-is. Applied patches are simply disabled for traceability. Fixes #926
2024-10-02 17:14:09 +07:00
<record model="res.groups" id="group_patcher">
<field name="name">Mergebot Patcher</field>
[FIX] runbot_merge: global acl removed on subtype access Because of tracking, `test_patch_acl` needs access to message subtypes during patch creation. If the user *only* has `runbot_merge.group_patcher` or `runbot_merge.group_admin` they don't have any of the "core" user groups (public, portal, internal) and thus don't have access to mail subtypes. Fix that by having the runbot_merge groups imply being an internal user.
2024-11-20 18:35:19 +07:00
<field name="implied_ids" eval="[
(4, ref('base.group_user')),
]"/>
[ADD] runbot_merge: support for unstaged patches Unstaged changes can be useful or necessary for some tasks e.g. absolute emergency (where even faking the state of a staging is not really desirable, if that's even possible anymore), or changes which are so broad they're difficult to stage (e.g. t10s updates). Add a new object which serves as a queue for patch to direct-apply, with support for either text patches (udiff style out of git show or format-patch) or commits to cherry-pick. In the former case, the part of the show / format-patch before the diff itself is used for the commit metadata (author, committer, dates, message) whereas for the commit version the commit itself is reused as-is. Applied patches are simply disabled for traceability. Fixes #926
2024-10-02 17:14:09 +07:00
</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
<record model="res.groups" id="group_admin">
<field name="name">Mergebot Administrator</field>
[FIX] runbot_merge: global acl removed on subtype access Because of tracking, `test_patch_acl` needs access to message subtypes during patch creation. If the user *only* has `runbot_merge.group_patcher` or `runbot_merge.group_admin` they don't have any of the "core" user groups (public, portal, internal) and thus don't have access to mail subtypes. Fix that by having the runbot_merge groups imply being an internal user.
2024-11-20 18:35:19 +07:00
<field name="implied_ids" eval="[
(4, ref('base.group_user')),
]"/>
[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
</record>
<record model="res.groups" id="base.group_system">
[ADD] runbot_merge: support for unstaged patches Unstaged changes can be useful or necessary for some tasks e.g. absolute emergency (where even faking the state of a staging is not really desirable, if that's even possible anymore), or changes which are so broad they're difficult to stage (e.g. t10s updates). Add a new object which serves as a queue for patch to direct-apply, with support for either text patches (udiff style out of git show or format-patch) or commits to cherry-pick. In the former case, the part of the show / format-patch before the diff itself is used for the commit metadata (author, committer, dates, message) whereas for the commit version the commit itself is reused as-is. Applied patches are simply disabled for traceability. Fixes #926
2024-10-02 17:14:09 +07:00
<field name="implied_ids" eval="[
(4, ref('runbot_merge.group_admin')),
(4, ref('runbot_merge.group_patcher')),
]"/>
[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
</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>
Reference in New Issue Copy Permalink