I believe we are experiencing the same issue that others are in this PR and are just waiting for it to merge: https://github.com/jenkinsci/github-branch-source-plugin/pull/134
On Friday, June 9, 2017 at 4:13:48 PM UTC-4, David Brooks 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. > > 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/73b0b77d-a634-435a-8feb-aacfa145e540%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
