Skip to content

Commit

Permalink
ci: Configure $CI_JOB_NAME correctly
Browse files Browse the repository at this point in the history
Looks like some env vars were tweaked on Azure's side of things, so
update how we configure `CI_JOB_NAME`.
  • Loading branch information
alexcrichton committed Jul 9, 2019
1 parent 78ca1bd commit 0efc7e3
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion .azure-pipelines/steps/run.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 0efc7e3

Please sign in to comment.