Skip to content

Commit

Permalink
[ci] Pass more information to the signing job (#5403)
Browse files Browse the repository at this point in the history
Context: 60ab195

Provide additional useful information regarding the build which is
calling the signing job.  When the build definition name and build
number is passed, the signing job will set the build number to reflect
the calling build.  This makes it much more convenient to immediately
tell which build launched the signing job without having to dig into
the logs.

It also leads to better information in our telemetry regarding the calling build.
  • Loading branch information
mjbond-msft authored Dec 10, 2020
1 parent f029ab7 commit f18b836
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion build-tools/automation/azure-pipelines.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -1251,6 +1251,6 @@ stages:
branchToUse: 'full-esrp-integration'
waitForQueuedBuildsToFinish: true
storeInEnvironmentVariable: true
buildParameters: '{ "REPO": "$(Build.Repository.Name)", "COMMIT": "$(Build.SourceVersion)", "SIGN_TYPE": "Real", "GITHUB_CONTEXT": "$(GitHub.Artifacts.Context)" }'
buildParameters: '{ "REPO": "$(Build.Repository.Name)", "COMMIT": "$(Build.SourceVersion)", "SIGN_TYPE": "Real", "GITHUB_CONTEXT": "$(GitHub.Artifacts.Context)", "BUILD_DEFINITIONNAME": "$(Build.DefinitionName)", "BUILD_ID": "$(Build.BuildId)", "BUILD_NUMBER": "$(Build.BuildNumber)", "BUILD_URI": "$(Build.BuildUri)" }'
authenticationMethod: 'OAuth Token'
password: $(System.AccessToken) # Equivalent to the 'Allow scripts to access OAuth token option': https://stackoverflow.com/questions/52837980/how-to-allow-scripts-to-access-oauth-token-from-yaml-builds

0 comments on commit f18b836

Please sign in to comment.