The 1st job does not need poll. If you have Github plugin and have configured and installed github-webhook on the source git repository on GitHub, you enable it to trigger with Github build trigger ³Build when a change is pushed to GitHub².
You can only associate the pipeline with the source repo if you also commit the jenkinsFile into the same source repo. On 11/10/16, 2:17 PM, "jenkinsci-users@googlegroups.com on behalf of Cory Grubbs" <jenkinsci-users@googlegroups.com on behalf of cagrubb...@gmail.com> wrote: >The whole objective is to get away from poll based CI as it places >unnecessary and unsustainable load on both the source control system and >Jenkins when you have thousands of projects continuously polling. In >addition this is not a scalable/efficient solution in that you would have >to create 2 Jenkins projects for every single build job. > >This is why I'm looking for a way to associate a pipeline project to a >specific github repo so that the webhook knows which project to execute >when invoked from github. > >-- >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/b2a91747-43ba-4cfa-8462- >3b57b5253620%40googlegroups.com. >For more options, visit https://groups.google.com/d/optout. -- 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/D44A5A1E.5FA86%25ingunawa%40cisco.com. For more options, visit https://groups.google.com/d/optout.
