Integrated: 1199: Enforce maintainer approval in JBS before allowing to integrate backports into updates projects
Zhao Song
zsong at openjdk.org
Mon Aug 14 17:20:26 UTC 2023
On Tue, 27 Jun 2023 21:37:35 GMT, Zhao Song <zsong at openjdk.org> wrote:
> As Erik said in the description of this issue, currently, this issue only cares about tracking approval labels in the related bugs.
>
> If a repository is set up with the "approval" configuration, pull requests in that repository will require the maintainer's approval in JBS. Otherwise, the pull request will not be considered ready.
>
> Erik has also provided a design outlining how to configure the "approval" for a repository.
>
>
> The simple case, where the labels are the same for every branch in a repository:
>
> "approval": {
> "request": "jdk17u-fix-request",
> "approved": "jdk17u-fix-yes",
> "rejected": "jdk17u-fix-no",
> }
>
> To reduce the need for changing multiple strings when copying a configuration for a new repository, there is an optional "prefix" field:
>
> "approval": {
> "prefix": "jdk17u-fix-",
> "request": "request",
> "approved": "yes",
> "rejected": "no",
> }
>
> When there are multiple branches with different labels, having the prefix set per branch can help reduce the size of the configuration significantly:
>
> "approval": {
> "request": "-critical-request",
> "approved": "-critical-approved",
> "rejected": "-critical-rejected",
> "branches": [
> "jdk20\.0\.1": { "prefix": "CPU23_04" }
> ]
> }
This pull request has now been integrated.
Changeset: bfaf1781
Author: Zhao Song <zsong at openjdk.org>
URL: https://git.openjdk.org/skara/commit/bfaf1781130e426fd7a328804f92e4629331eec4
Stats: 399 lines in 9 files changed: 378 ins; 4 del; 17 mod
1199: Enforce maintainer approval in JBS before allowing to integrate backports into updates projects
Reviewed-by: erikj
-------------
PR: https://git.openjdk.org/skara/pull/1537
More information about the skara-dev
mailing list