tag:help.appveyor.com,2012-11-13:/discussions/problems/24317-worker-cli-oddness-with-popdAppVeyor: Discussion 2019-10-14T21:01:26Ztag:help.appveyor.com,2012-11-13:Comment/474174542019-07-16T19:47:53Z2019-08-15T00:20:48ZWorker CLI oddness with popd<div><p>Hello. Has this issue been reviewed yet?</p></div>feamsr00tag:help.appveyor.com,2012-11-13:Comment/474174542019-07-17T05:14:37Z2019-07-17T05:14:37ZWorker CLI oddness with popd<div><p>Sorry for the delay, we just saw it today as it got caught up in some spam filter.<br>
Reviewing now.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/474174542019-07-17T08:02:16Z2019-07-17T08:02:16ZWorker CLI oddness with popd<div><p>It is because AppVeyor starts every <code>CMD</code> command as a new process and it does not "remember" location saved by <code>pushd</code>. Something like <code>pushd adir && cd && popd</code> should work, or you can wrap it into the batch file. If you prefer commands line-by-line in AppVeyor build configuration, you can also use PowerShell (which runs in the same session) <code>Pop-Location</code> and <code>Push-Location</code> commands.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/474174542019-08-11T04:18:57Z2019-08-15T00:20:49ZWorker CLI oddness with popd<div><p>Hello Ilya and thanks for the reply here. Could you help me understand this behavior? What is the rationale behind spinning a new cmd for every line and not having the build process, say, make a temp batch file? What are the implications for environment vars?</p></div>feamsr00tag:help.appveyor.com,2012-11-13:Comment/474174542019-08-14T18:03:51Z2019-08-14T18:03:51ZWorker CLI oddness with popd<div><p>I think the reason was proper error handling. No implications on environment variables.</p></div>Ilya Finkelshteyn