Hello. I often see this behavior. You can see why a build is kicked in "Polling Log".
I know builds are kicked without SCM change when following cases: * When there is no workspace for that project. Especially when polling run on a slave where a build of that project have never run. * When polling failed. I resolved this by enabling "Fast remote polling" in "Advanced..." of Git plugin configuration. It gets to check changes by only seeing remote SHA1 of the latest commit. This feature requires only one entry in "Branches to build" without wildcards. See help for details. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
