Your theory is correct. The git-plugin will list every branch revision,
filter out non-top revision (branches that are fully merged in another
branch) and then build them one by one, oldest commit first.
Once you've built all there is to build, only changes will build.
Maybe you could consider e
Hey, this has happened to me twice on two different Ubuntu 10.04 servers
running a fresh install of Jenkins 1.457.
I install the Git and GitHub plugins and configure my new Jenkins job to
build when it receives a push notification from GitHub. In the job
config I leave "Branches to build - Branch
