Workaround coreclr issue (#16828)

VSTS does not seem to be correctly honoring the working directory for batch script steps. Explicitly qualify the setup_vs_env.cmd path
dotnet · Mar 8, 2018 · 03dd0ba · 03dd0ba
1 parent c9eaaac
commit 03dd0ba
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/buildpipeline/DotNet-Trusted-Publish.json b/buildpipeline/DotNet-Trusted-Publish.json
@@ -79,10 +79,10 @@
         "definitionType": "task"
       },
       "inputs": {
-        "filename": "setup_vs_tools.cmd",
+        "filename": "$(Pipeline.SourcesDirectory)\\setup_vs_tools.cmd",
         "arguments": "",
         "modifyEnvironment": "true",
-        "workingFolder": "$(Pipeline.SourcesDirectory)",
+        "workingFolder": "",
         "failOnStandardError": "false"
       }
     },
@@ -758,4 +758,4 @@
     "revision": 418098432,
     "visibility": "organization"
   }
-}
+}