Checking out consistent git revision across stages

[Asa Riley]

I have a stage for building my application, and another stage for running integration tests. As I understand it, each job that needs the source must checkout the source again, so what happens if someone commits during the build stage? Will the integration step phase include the newest commit? Or will it somehow be locked to the revision of the source used in the build stage? 

[Asa Riley]

Ok, I think the answer is that the revision number is locked for the whole build of a plan. I haven't found this explicitly stated in the documentation, but I did find the following which implies this is the case:

"If the child build uses the same source as the parent build (for example, the Subversion URL is the same), the child build will be forced to check out the same revision of source code as the parent build. This ensures that builds are consistent when triggering one build from another."