Looks like some env vars were tweaked on Azure's side of things, so update how we configure `CI_JOB_NAME`.
try