-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Yarn to the VS2017 Hosted agent #4757
Comments
You can also do curl download. Only npm one isn't signed https://yarnpkg.com/lang/en/docs/install/#alternatives-tab We won't be adding all the misc tools to the hosted convenience image. That image is VS2017 full install. The other alternative is a private agent on your own VM |
@bryanmacfarlane : Do we have curl installed in Hosted VS2017? If i check list of software installed in Hosted 2017, The reason we are moving to yarn is because bower will soon be discontinued and, as an alternate bower's developers are recommending switching to yarn. bower readme.md Hosted agent 2017 has bower installed out of the box, that's where we were hoping to get yarn installed before bower is discontinued. |
@amitse |
I tried installing yarn on a VSTS Hosted agent, but it did not work. When I pick a Ubuntu 16.04 machine,
Installing Yarn on a standard Hosted agent does not work too because it does not come with choco:
On a Hosted VS2017 agent, choco install log
How do you folks run yarn on Hosted agents (both Windows and Ubuntu)? UPD: Replacing the custom yarn task with a simple cmd call to
|
@kachkaev You're correct, I had the exact same issue. I assume the environment variables aren't refreshed correctly after installing yarn through chocolatey. I switched to npm because this was taking way to long to get it working... |
We can't switch to npm as we're relying on Yarn these days seems to be as popular as npm, so it'd be great to see it in VSTS Hosted agents by default. Docker |
Please consider adding
yarn
to the VS2017 Hosted agent.Currently we've following alternatives
npm install yarn
is also not a good idea as the package won't be signed, and the only integrity check performed is a basic SHA1 hash, which is a security riskThanks
The text was updated successfully, but these errors were encountered: