2.0: rebuild gives different CIRCLE_SHA1 value

When doing a rebuild I notice that the CIRCLE_SHA1 value is changed to a value that is not part of the current git repo. The original build has a SHA that is linked to the GIT sha, but the rebuilds does not match.

This is only apparent in 2.0, but breaks our deploy pipeline as a rebuild need the original gith(hub) sha to be able to trigger the next steps in our private pipeline.

Hm, maybe I fired too fast. I can’t find the build that showed these characteristics… Maybe I messed this up :blush: