Skip to content
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

RE: jekyll/_docs/yarn.md #551

Closed
itaysabato opened this issue Jan 23, 2017 · 7 comments
Closed

RE: jekyll/_docs/yarn.md #551

itaysabato opened this issue Jan 23, 2017 · 7 comments

Comments

@itaysabato
Copy link

The new docs page about yarn integration does not specify how to pass CircleCI the desired yarn version - hopefully, there is a way to do that...

Thanks.

@felicianotech
Copy link
Contributor

With Yarn pre-installed, there is no longer a way to do this. I'm assuming this is because you want to use the latest version?

I'm not sure the best way to update Yarn manually with this issue currently in discussion: yarnpkg/yarn#1139

@itaysabato
Copy link
Author

Since yarn is still new technology I would like to be able to have control over which version is running in all my builds (and make sure it is in sync with all my other environments). If CircleCI will always install the latest stable version it would probably be OK though for the most part.

If this is the case, I believe it should be documented along with the current pre-installed version.

@itaysabato
Copy link
Author

@felicianotech I appreciate the quick response BTW! :)
Thanks

@felicianotech
Copy link
Contributor

felicianotech commented Jan 23, 2017

At the moment, Yarn is being managed the same way most software, including NPM is managed on CircleCI 1.0. The CCI Ubuntu 14.04 image is created every couple of months and it's within this window where we try to update the software it contains. Once an image is cut (this is the latest), the software is frozen at that version until the next update. The 'Announcements' category on CircleCI Discuss can be used to follow these announcements.

This is the process we use currently to try and balance the need by many developers to have newer versions of tools vs the strain and stress constant updates can cause both developers and our infrastructure (the image is large).

Once the Yarn Team figures out a way to fix yarn self-update (re: the link I first posted), then we can update this doc to include instructions on how to update Yarn automatically during a build.

Update:

"I appreciate the quick response BTW! :)
Thanks"

Not a problem. I'm trying to give this repo the attention it deserves. All this feedback from users is what makes docs great and gives us the opportunity to improve.

@itaysabato
Copy link
Author

Thanks, I have certainly been informed :)

I'll be sure to keep up with the image updates from now on.

@felicianotech
Copy link
Contributor

No problem.

@moretti
Copy link

moretti commented Feb 23, 2017

@felicianotech Do you know if there's any temporary workaround?
I tried with:

dependencies:
  pre:
    # Upgrade Yarn
    - curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
    - echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
    - sudo apt-get update && sudo apt-get install yarn

But it doesn't seem to work:

Preparing to unpack .../archives/yarn_0.20.3-1_all.deb ...
Unpacking yarn (0.20.3-1) ...
Setting up yarn (0.20.3-1) ...

yarn install v0.18.1 <- 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants