Hi Stephen, Our API token currently has repo, read:org, admin:repo_hook, user:email. What else are we missing? I don't see an explicit option for repo:admin
On Monday, June 12, 2017 at 8:32:16 AM UTC-4, Stephen Connolly wrote: > > > On Mon 12 Jun 2017 at 13:15, David Brooks <[email protected] > <javascript:>> wrote: > >> So the only way for Jenkins to use a Jenkinsfile to build/test a PR is by >> having that Jenkinsfile already merged into master? How do you test updates >> to your Jenkinsfile? >> > > Give Jenkins an api token with repo:admin permissions and then it can see > the collaborators > > That's the "today" solution > > Next week should have different answers (may even be this week if I can > avoid interruptions) > > >> >> On Saturday, June 10, 2017 at 8:18:58 AM UTC-4, Stephen Connolly wrote: >>> >>> >>> On Fri 9 Jun 2017 at 21:13, David Brooks <[email protected]> wrote: >>> >>>> Hey all, >>>> >>>> We currently have a GitHub Organization Folder that is told to build >>>> projects that have a Jenkinsfile in their root. However, when I create a >>>> branch with a brand new Jenkinsfile on a repo that never had a Jenkinsfile >>>> before, the PR is not being built using the Jenkinsfile in the PR. I read >>>> https://support.cloudbees.com/hc/en-us/articles/227246367-Why-Jenkinsfile-changes-Are-Not-Reflected-in-PR-Build >>>> >>>> but don't understand why I was not a trusted source. I am an Admin of our >>>> GitHub organization and a team I am apart of was added to this specific >>>> repo with Write access. >>>> >>>> I don't want to merge in the Jenkinsfile without it first being run and >>>> tested. It seems as if this issue was addressed in >>>> https://github.com/jenkinsci/github-branch-source-plugin/pull/114 and >>>> tag github-branch-source-2.01 however, my Jenkins is running version 2.06 >>>> so I don't understand why this is still occurring. >>>> >>> >>> Jenkins does not have permission to query collaborators >>> >> >>>> Any ideas are welcomed! >>>> >>>> Thanks, >>>> David >>>> >>>> -- >>>> 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/a329e568-0cb3-47d6-8138-4a6c69cbae82%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/a329e568-0cb3-47d6-8138-4a6c69cbae82%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> Sent from my phone >>> >> -- >> 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/53da2e6e-89f6-4646-8a35-ff18358510ec%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/53da2e6e-89f6-4646-8a35-ff18358510ec%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > Sent from my phone > -- 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/14ad603a-b7bc-4955-bdb3-38aeaee1d0a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
