Yarn installation fails if Yarn policies are in use

[circleci-public]

Yarn installation fails if Yarn policies are in use

[Jaryt]

@gggritso I see! Thanks for that description of the issue. Seems like the way forward would be to automatically alias (todo: confirm that is what yarn is actually doing in the set-version script) to the yarn-path included in either of the yarnrc files. Will work on getting this in this week 👍

[Jaryt]

Thanks! Will take a look into this and get back to you shortly 👍

[Jaryt]

Hi @gggritso Sorry for the delay here, had my hands full with some other tasks. I'm implementing the fix right now, and the solution actually quite simple. Since the yarn --version command is being called while your project is the working directory, it's picking up the version from the yarn path locally. So, the only change necessary is to change the working directory to home so that it uses the yarn --version from the actual yarn binary.

[Jaryt]

Confirmed fixed 😄

Will be in next fix release!

[techpeace]

This was reported in the community forum, and I've also been running into it. A user there reported that they tracked it down to a certificate check.

[Jaryt]

Hi! After looking into this further, I'm wondering if installing yarn here is redundant as it looks like the .yarn/releases folder is allows yarn to be managed via source control. What behavior do you experience when you remove the install-yarn parameter?

[gggritso]

@Jaryt I agree, it would be better to use the executable in .yarn/releases, but there's no clean mechanism to do so! The behaviour we experience is that the yarn command fails, because there isn't a yarn command, and we use yarn to run tasks like yarn test.

We alias .yarn/releases/yarn-1.22.11.js to yarn to overcome this. It's fine, but a little gross because we have to either hard-code the Yarn version in our CircleCI config or we have to iterate through the contents of .yarn/releases to find the file, and create an alias.

The first option is a little frustrating because we'd have to update the file any time we upgrade Yarn. The second version works better, but is a little messy. Mostly, it's just surprising that the installation fully fails if Yarn policies are used.

[gggritso]

@Jaryt that's great, thank you!

[gggritso]

@Jaryt thank you very much for fixing this!