From 0efc7e3898d840be0870a52b0dbaab50bad4fabd Mon Sep 17 00:00:00 2001 From: Alex Crichton Date: Tue, 9 Jul 2019 09:09:13 -0700 Subject: [PATCH] ci: Configure $CI_JOB_NAME correctly Looks like some env vars were tweaked on Azure's side of things, so update how we configure `CI_JOB_NAME`. --- .azure-pipelines/steps/run.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.azure-pipelines/steps/run.yml b/.azure-pipelines/steps/run.yml index 1ece3ceb088a0..9e6fb6c8a8c51 100644 --- a/.azure-pipelines/steps/run.yml +++ b/.azure-pipelines/steps/run.yml @@ -100,7 +100,9 @@ steps: # Configure our CI_JOB_NAME variable which log analyzers can use for the main # step to see what's going on. -- bash: echo "##vso[task.setvariable variable=CI_JOB_NAME]$SYSTEM_JOBNAME" +- bash: | + builder=$(echo $AGENT_JOBNAME | cut -d ' ' -f 2) + echo "##vso[task.setvariable variable=CI_JOB_NAME]$builder" displayName: Configure Job Name # As a quick smoke check on the otherwise very fast mingw-check linux builder