Thanks Damian! I saw that the config also has this:
  orgWhitelist(['apache'])
Shouldn't that be enough to allow all Apache committers?

I traced the code for the membership check here:
https://github.com/jenkinsci/ghprb-plugin/blob/4e86ed47a96a01eeaa51a479ff604252109635f6/src/main/java/org/jenkinsci/plugins/ghprb/GhprbGitHub.java#L27
Is there a way to see these logs?


On Thu, Jul 23, 2020 at 7:08 AM Damian Gadomski <damian.gadom...@polidea.com>
wrote:

> Hi,
>
> You are right, the current behavior is wrong, I'm currently working to fix
> it asap. Our intention was to disable that only for non-committers.
>
> As a workaround, as a committer, you could manually add yourself (your
> GitHub username) to the whitelist of the SeedJob configuration:
> https://ci-beam.apache.org/job/beam_SeedJob/configure
> Then, your comment "Run Seed Job" will trigger the build. I've already
> manually triggered it for you that way.
>
> Of course, it will only work until the seed job gets executed - it will
> then override the whitelist with an empty one.
>
> [image: Selection_408.png]
>
> As a target solution, I'm planning to fetch the list of beam committers
> from LDAP and automatically add them to the whitelist above as a part of
> the seed job. I'll keep you updated about the progress.
>
> Regards,
> Damian
>
>
> On Wed, Jul 22, 2020 at 11:03 PM Ahmet Altay <al...@google.com> wrote:
>
>> +Damian Gadomski <damian.gadom...@polidea.com>, it might be related to
>> this change: https://github.com/apache/beam/pull/12319.
>>
>> /cc +Tyson Hamilton <tyso...@google.com>
>>
>> On Wed, Jul 22, 2020 at 1:17 PM Udi Meiri <eh...@google.com> wrote:
>>
>>> HI,
>>> I'm trying to test a groovy change but I can't seem to trigger the seed
>>> job. It worked yesterday so I'm not sure what changed.
>>>
>>> https://github.com/apache/beam/pull/12326
>>>
>>>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to