force multi steps to use the same commit in CI#7697
Merged
Conversation
edgchen1
reviewed
May 14, 2021
| fetchDepth: 1 | ||
| submodules: false | ||
| - script: | | ||
| echo.$(Build.SourceVersion) |
Contributor
There was a problem hiding this comment.
just curious, does this mean that $(Build.SourceVersion) can change within a single build?
Contributor
Author
There was a problem hiding this comment.
if it is a PR build, yes.
each job in the pipeline will checkout ref/pull/<PR_ID>/merge. and this may be different if the master is updated.
hanbitmyths
approved these changes
May 14, 2021
snnn
approved these changes
May 14, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description: extract the commit of the CI job and checkout them in all steps. this resolves the inconsistency of wasm building pipeline