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 d...@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?
