When uploading buildkite:git:commit metadata, subsequently created jobs within that build will reflect that commit, however, previously-uploaded (but still targeting “HEAD”) jobs will not. This can cause race conditions where different steps are pointed at different commits.
It seems as though any subsequently started jobs should use the backfilled meta-data, rather than only those created after the meta-data is set.
The case in question is a pipeline authored using the YAML pipeline editor beta, so there is no pipeline upload in between the pipeline starting and jobs existing!
When uploading
buildkite:git:commit
metadata, subsequently created jobs within that build will reflect that commit, however, previously-uploaded (but still targeting “HEAD”) jobs will not. This can cause race conditions where different steps are pointed at different commits.It seems as though any subsequently started jobs should use the backfilled meta-data, rather than only those created after the meta-data is set.