I am +1 for installation.
The only concern are the org-level hooks, but I think we can live with that 
in jenkinsci where we have no private repos

On Wednesday, April 1, 2020 at 4:29:18 PM UTC+2, Ullrich Hafner wrote:
>
> Since this is an opt-in for all Jenkins projects maybe it is not so 
> problematic to install it. Then team admins can use it if they like. I use 
> it for almost two years now without any problems. (I think we can remove it 
> later on, if our GitHubs checks integration is available…).
>
>
> Am 23.03.2020 um 01:27 schrieb Oleg Nenashev <[email protected] 
> <javascript:>>:
>
> Hi Ulli,
>
> Is it possible to grant individual users a permission to enable apps in 
>> their repositories? Or is this something that needs to be done for the 
>> whole org?
>>
>
> Once an app is approved for an organization, any plugin maintainer with 
> Admin permissions will be able to add their plugin repositories to an App 
> This is how we manage the most of the apps  nowadays, including Dependabot 
> or Release Drafter.
> Any new GitHub App requires review, because they tend to require a lot of 
> permissions nowadays. E.g. Here is what Codacy asks for.
>
>    - No access to code
>    - Read access to members and metadata
>    - Read and write access to checks, commit statuses, issues, 
>    organization hooks, pull requests, and repository hooks
>
> If there is no concerns, I can review the app in the next few days
>
> Is someone of our GitHub admins receiving such requests? Or where are 
>> these requests routed to?
>>
> Yes, GitHub org admins receive and process such requests.
> You can create an INFRA ticket as an alternate way.
>
> Hopefully it helps,
> Oleg
>
>
>  
>
> On Sunday, March 22, 2020 at 4:01:09 PM UTC+1, Ullrich Hafner wrote:
>>
>> I'm currently using Codacy (https://www.codacy.com/) to validate PRs on 
>> my Jenkins repositories to check for CheckStyle and PMD warnings. Up to now 
>> I can activate this app on a per repository basis. 
>>
>> But they now switch the integration and are now available as a GitHub 
>> App. So when I want to enable the App for my repository I get the following 
>> dialog:
>>
>>
>>
>> In this dialog I cannot enable the access for an individual repository, I 
>> just can create a `request`. Is someone of our GitHub admins receiving such 
>> requests? Or where are these requests routed to?
>>
>> I also wanted to enable the Settings App (
>> https://probot.github.io/apps/settings/) to set the labels of all of my 
>> repositories to the same set of labels. Here I have the same problem: I can 
>> activate them for my repositories in my account (i.e. uhafner/*) but not 
>> for a repository in jenkinsci. 
>>
>> Is it possible to grant individual users a permission to enable apps in 
>> their repositories? Or is this something that needs to be done for the 
>> whole org?
>>
>>
>>
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/87de0d08-1845-4782-ac37-c6a3a97d23e6%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/87de0d08-1845-4782-ac37-c6a3a97d23e6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9003efc9-6891-4fb5-b552-27beeb1baae4%40googlegroups.com.

Reply via email to