Ok....still doesn't solve the problem of having to have two separate Jenkins projects for every build which is not efficient nor scalable to the level I need it to be.
I find it hard to believe you can't configure a webhook on a github repo to kick off a specific Jenkins job that isn't connected to the repo but I sure can't figure out how. What is the purpose of the Github project field within the Jenkins job configuration if it doesn't create the necessary association for webhooks to invoke the job when changes are pushed to the specified github repo? Cory -- 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/11eac010-ef97-4eba-9123-ab7bd4eff432%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
