Spurious build triggerred with SCM change - git plugin

[Ramesh S]

I had a spurious job triggerred on an inactive git branch after a long time (2 weeks)

There were no changes to the branch that's supposed to be built.

Build N and N+1 show the same commit id as the 'built' version. Bulid N+1 says 'triggerred by SCM change'

Is there any specific reason it would happen ? I am using version 1.393 on Ubuntu machine.

Any help would be appreciated.

Thanks and regards,

VSRamesh.

[Andrew Bayer]

Take a look at the Polling Log for build n+1 - I'd bet that it says it ran because there was no available workspace. The git plugin needs a workspace to be able to poll, so if the workspace for a job gets deleted/cleared/etc, the next time the git plugin goes to poll, it sees no workspace and runs a build to get a fresh one. I wonder if it may make sense to change that to just pull down the workspace if there's a known previous state to compare against, so that it doesn't need to run a whole build - I'll look into that.

A.