Re: Any plans for the github checks API?

+1 "ChatOps" triggers would be highly beneficial thereby letting the github-branch-source to run the required checks on specific parts. Also detailed reports from GitHub Checks could be published and maybe parsed as required. On Mon, Jan 27, 2020, 6:27 PM Oleg Nenashev wrote: > Just to bump

Re: What is the best approach for mutually exclusive permissions - re: proposed Jenkins.CONFIGURE and Jenkins.SYSTEM_READ permissions

Perfect thanks Michael On Mon, 27 Jan 2020 at 15:21, Michael Cirioli wrote: > Tim, > > I've added a section to our proposed JEP-223 > committing to work > with you on the Jenkins.SYSTEM_READ effort so that we can find a way to > provide

Re: Any plans for the github checks API?

+1 would be great, I've done some ground laying work for it here: https://github.com/jenkinsci/github-branch-source-plugin/pull/269 It requires a github-api-plugin version to be published with a recent ish version of github-api Thanks Tim On Mon, 27 Jan 2020 at 16:09, Raihaan Shouhell wrote:

Re: Proposal: Expanding the Jenkins Core maintainers team

I was under the impression that a CCLA has to be filed first, is my assumption wrong? I'm currently in the process of getting that sorted out On Monday, 27 January 2020 04:31:06 UTC+8, Oleg Nenashev wrote: > > One thing to mention is that I will be traveling on Jan 29 ... Feb 08: > FOSDEM and

Re: Any plans for the github checks API?

I think having a checks api would be great. Reports sending checks back to the change request would be a useful feature. On Monday, 27 January 2020 20:57:31 UTC+8, Oleg Nenashev wrote: > > Just to bump this thread, we consider adding Checks API integration as a > GSoC 2020 project idea. > We

Re: What is the best approach for mutually exclusive permissions - re: proposed Jenkins.CONFIGURE and Jenkins.SYSTEM_READ permissions

Tim, I've added a section to our proposed JEP-223 committing to work with you on the Jenkins.SYSTEM_READ effort so that we can find a way to provide both of these features to the user in a way that makes sense and provides a non-confusing

Re: JEPs & BDFL ~ KK

On Sun, Jan 26, 2020 at 4:28 PM Oleg Nenashev wrote: > [the JEP process] does not achieve its main purpose - facilitate the > community feedback, help JEP submitters to get their changes delivered, and > to ensure that all changes are net-positive for the Jenkins project and > beneficial for

Re: Any plans for the github checks API?

Just to bump this thread, we consider adding Checks API integration as a GSoC 2020 project idea. We had a preliminary discussion with Ulli Hafner (Warnings NG) and other parties. If someone is interested to join the project, please let me know On Thursday, May 10, 2018 at 5:56:28 PM UTC+2,

Re: Proposal: Automatically requesting code reviews from plugin developer teams (CODEOWNERS)

> The default for a team is "secret" which means members are not visible to anyone, the only other option available is "closed" which means the members are visible only to members of the organization, not the general public. I think since it is not exposed to the general public that this should be