You could potentially use a build strategy to only build PRs that
contain one or more labels on the PR, and labels can only be added by
committers by default. I've used this plugin at work recently for
building an opt-in acceptance test pipeline:
https://plugins.jenkins.io/github-label-filter/
On
> On Aug 14, 2020, at 4:01 PM, Richard Eckart de Castilho
> wrote:
>
> Hi,
>
>> On 30. Jul 2020, at 05:42, Chris Lambertus wrote:
>>
>> There is no policy per-se, we have done this in the past, specifically for
>> repo:status tokens;
>>
>> Please create an infra jira ticket. Unfortunatel
Hi,
> On 30. Jul 2020, at 05:42, Chris Lambertus wrote:
>
> There is no policy per-se, we have done this in the past, specifically for
> repo:status tokens;
>
> Please create an infra jira ticket. Unfortunately, it’s an extremely manual
> process on our end, and requires Infra to create and m
Hi,
On Tue, Aug 11, 2020 at 9:12 PM Zoran Regvart wrote:
> Hi Chris and Builders,
> there is an online meetup on the Jenkins and GitHub App support that
> you might be interested in:
>
> https://www.meetup.com/Jenkins-online-meetup/events/272504950/
>
>
Thanks, and interesting timing, I installe
Hi Chris and Builders,
there is an online meetup on the Jenkins and GitHub App support that
you might be interested in:
https://www.meetup.com/Jenkins-online-meetup/events/272504950/
zoran
On Thu, Jul 30, 2020 at 11:04 PM Chris Lambertus wrote:
>
>
>
> > On Jul 30, 2020, at 1:50 PM, Zoran Regva
> On Jul 30, 2020, at 1:50 PM, Zoran Regvart wrote:
>
> Hi Chris,
>
> On Thu, Jul 30, 2020 at 5:42 AM Chris Lambertus wrote:
>> Please create an infra jira ticket. Unfortunately, it’s an extremely manual
>> process on our end, and requires Infra to create and maintain an account and
>> pas
Hi Chris,
On Thu, Jul 30, 2020 at 5:42 AM Chris Lambertus wrote:
> Please create an infra jira ticket. Unfortunately, it’s an extremely manual
> process on our end, and requires Infra to create and maintain an account and
> password+token for each project, so it’s something we try to avoid unle
Thanks Chris.
I created a ticket for ZooKeeper:
https://issues.apache.org/jira/browse/INFRA-20613
...and saw you already responded.
Andor
> On 2020. Jul 30., at 5:42, Chris Lambertus wrote:
>
> There is no policy per-se, we have done this in the past, specifically for
> repo:status tokens
There is no policy per-se, we have done this in the past, specifically for
repo:status tokens;
INFRA-19879
INFRA-20042
Please create an infra jira ticket. Unfortunately, it’s an extremely manual
process on our end, and requires Infra to create and maintain an account and
password+token for eac
Infra hasn't approved these in the past. If that policy changes, I'd
very much like to know about it.
For CouchDB we use a token on my account that I added for this purpose,
limited to Apache repos only. Of course, these API calls count towards
my personal limit, which affects other GitHub wor
I’ve created a dummy Github user for ZooKeeper, it works fine in terms of
branch scanning, but it doesn’t have permissions to update the Github Build
status at the end of each build.
I think I should add it to the project as contributor/member, but not sure how
to do that.
Please advise.
Ando
I’m interested in this one too.
Currently I’m using regular ‘Git’ source instead of GitHub to speed up branch
discovery, but this way I cannot run builds against Pull Requests.
Andor
> On 2020. Jul 23., at 21:38, Zoran Regvart wrote:
>
> Hi builders,
> I see some questions on this but not mu
Hi builders,
I see some questions on this but not much conclusion currently.
What credentials should we use with GitHub SCM source? Should we use
personal access tokens, or will there be an INFRA provided
Jenkins-wide credential we can use (like a GitHub App[1])?
We're now at the mercy of the Git
13 matches
Mail list logo
