https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#_controlling_what_is_built
Documentation mentions that "By default, Jenkins will build any branches it finds in the “origin” repository (the actual repository found in your organization). Also, any pull requests that have been filed from “forks” (clones in user accounts) will also be built . . ." In our setup, running Jenkins v.2.60.1 with this plugin v2.2.0, the latter usecase i.e. pull requests filed from forks is not triggering automatic builds -- user A forks a repo, commits his/her changes to 'master' in forked repo and then creates a pull request from the actual repo. I hope this is valid use case. So, does anyone know why this fails ? /Ram -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8043350c-1377-45cd-a04b-277cc2b9e7b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
