I've configured a post-receive hook in GitHub to hit the Jenkins notifyCommit
URL for my repository as described here.
Any commit, on any branch, triggers that hook, which sends a polling event. Fine. Make a change to a feature branch, and Jenkins will do its poll and notice that there's nothing new to build on the job's configured branch (master), right?
But apparently, not, because even though the Jenkins job polling log says:
[poll] Last Built Revision: Revision abc123 (origin/master)
Pushing to a new branch, origin/not-master
, triggers a build, whose log says:
Checking out Revision abc123 (origin/master)
So it's starting a new build for master when nothing has changed in master. Could this be a problem with how the job's repository and branch are configured? Or is this just how scheduled polling works?