From 930a36df37e2e1d0b99be4b05ff822ce35982424 Mon Sep 17 00:00:00 2001 From: Ethan P <56270045+ethanpalm@users.noreply.github.com> Date: Mon, 13 Sep 2021 13:40:49 -0400 Subject: [PATCH] Add example step for ending build tracing --- .../codeql-cli/creating-codeql-databases.rst | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/codeql/codeql-cli/creating-codeql-databases.rst b/docs/codeql/codeql-cli/creating-codeql-databases.rst index f12f480524a..e007f88368c 100644 --- a/docs/codeql/codeql-cli/creating-codeql-databases.rst +++ b/docs/codeql/codeql-cli/creating-codeql-databases.rst @@ -324,7 +324,20 @@ The following example shows how you could use indirect build tracing in an Azure clean: True displayName: Visual Studio Build - # End build tracing. + # Read and set the generated environment variables to end build tracing. This is done in PowerShell in this example. + - task: PowerShell@1 + displayName: Set CodeQL environment variables + inputs: + targetType: inline + script: > + $json = Get-Content $(System.DefaultWorkingDirectory)/db/temp/tracingEnvironment/end-tracing.json | ConvertFrom-Json + $json.PSObject.Properties | ForEach-Object { + $template = "##vso[task.setvariable variable=" + $template += $_.Name + $template += "]" + $template += $_.Value + echo "$template" + } - task: CmdLine@2 displayName: Finalize CodeQL database