www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Hunt <ph...@cloudera.com>
Subject Re: Jenkins Github PR integration - Support for whitelisting?
Date Fri, 29 Sep 2017 15:01:33 GMT
We've been using this integration at ZooKeeper quite successfully as well.
Kudos!

I recently setup our job to allow "build with parameters" where the
parameter is the PR number. This is quite useful when the PR tests fail due
to, say, a flakey test and you want to re-run. It was a bit of a bear to
get this running, I looked at some docs I found on the web (the link to the
plugin in the original blog post is no longer valid) but I wasn't sure if
they corresponded to the same version in use on apache Jenkins. Is there
some place at apache where information is being shared?

Regards,

Patrick


On Thu, Sep 28, 2017 at 11:37 PM, Dominik Psenner <dpsenner@gmail.com>
wrote:

> On 2017-09-27 23:26, Meghna Baijal wrote:
>
>> Thanks Dominik! I looked at Log4net’s Jenkinsfile and it is going to be a
>> good reference for me in the future.
>> I am currently adding some features via the Jenkinsfile script and I am
>> hoping they will work as expected on Apache Jenkins :)
>>
> Thanks for the Kudos. Please note that the pipeline is not finished at all
> and lacks several important stages like publishing the generated site and
> built binaries on release branches and tags. In case you can make this work
> I would like to see how you made that work. Would you please ping here or
> dev@logging.apache.org when you've finished that?
>
> Please note further that we observed some strange things with log4net's
> build job. One is that the job at the end reports "Could not update commit
> status, please check if your scan credentials belong to a member of the
> organization or a collaborator of the repository and repo:status scope is
> selected". I assume that the github plugin would like to save a build
> status on the commit but is unable to do so because of a credential issue.
> I'm sure that I've granted repo:status on the credentials that jenkins uses
> and it is most likely because my github user is part of the apache
> organization but only the apache organization can save such changes. Does
> anyone know whether this is the case or not?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message