As the title describes, the behavior I'm seeing is not what I expect.

 

A build that fails is starting again, claiming there's an SCM change, but upon manual inspection, all commit hashes of these builds are identical.

 

Just now over the weekend a job ran over 500 times, with not a single push to the source repo to justify this.

 

Expected behavior: If a build fails, then it fails. No further action is to be taken by the build system itself, it is up to the developers to choose how to respond.

 

My system is running 2.440.2(sticking to LTS), I've been seeing this since a few versions ago, though I'm not sure exactly which. I think at least 2.426.2