Not honouring Project Directory setting

Question

Not honouring Project Directory setting

Mardoxx opened this issue 7 years ago · comments

I have a yarn install task with Project Directory set as $(System.DefaultWorkingDirectory)/Release/ApplicationPackageRoot/WebUIPkg/Code and the Production flag set.

Output is as follows:

2017-09-13T11:00:14.0838653Z [command]C:\Windows\system32\cmd.exe /D /S /C "C:\NPM\Modules\yarn.cmd --production install"
2017-09-13T11:00:14.5278652Z yarn install v1.0.1
2017-09-13T11:00:14.5638843Z info No lockfile found.
2017-09-13T11:00:14.5728658Z [1/4] Resolving packages...
2017-09-13T11:00:16.0594477Z [2/4] Fetching packages...
2017-09-13T11:00:19.3006297Z [3/4] Linking dependencies...
2017-09-13T11:00:20.6145066Z [4/4] Building fresh packages...
2017-09-13T11:00:20.6405089Z success Saved lockfile.
2017-09-13T11:00:20.6425069Z Done in 6.12s.

As in, it's running in the wrong directory!

If I use the npm task with identical settings it works fine.

Sandor · Answer 1 · Wed Sep 13 2017 19:36:36 GMT+0800 (China Standard Time)

The directory is set throw cwd , the log you are showing is perfectly fine. If you provide the full debug log we might be able to guide you a bit more Le mer. 13 sept. 2017 à 21:09, Mardoxx <notifications@github.com> a écrit :

…

I have a yarn install task with Project Directory set as $(System.DefaultWorkingDirectory)/Release/ApplicationPackageRoot/WebUIPkg/Code and the Production flag set. Output is as follows: 2017-09-13T11:00:14.0838653Z [command]C:\Windows\system32\cmd.exe /D /S /C "C:\NPM\Modules\yarn.cmd --production install" 2017-09-13T11:00:14.5278652Z yarn install v1.0.1 2017-09-13T11:00:14.5638843Z info No lockfile found. 2017-09-13T11:00:14.5728658Z [1/4] Resolving packages... 2017-09-13T11:00:16.0594477Z [2/4] Fetching packages... 2017-09-13T11:00:19.3006297Z [3/4] Linking dependencies... 2017-09-13T11:00:20.6145066Z [4/4] Building fresh packages... 2017-09-13T11:00:20.6405089Z success Saved lockfile. 2017-09-13T11:00:20.6425069Z Done in 6.12s. As in, it's running in the wrong directory! If I use the npm task with identical settings it works fine. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#25>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACiXpkQ-no0KZUQVTLnisrjNfo5lqbKLks5sh7fWgaJpZM4PV8dc> .

Mardoxx · Answer 2 · Mon Sep 18 2017 23:41:12 GMT+0800 (China Standard Time)

@sandorfr sorry! Package install was so quick I thought something was wrong. When deployed it was like nothing had installed, must be a different issue.

Thanks!