[FR] Yarn 2 out-of-the-box compatibility

[sylvainar]

Notice

To request a feature in the hosted Google Cloud Build service, please contact your Google Cloud Support representative or suggest your feature using Google's public issue tracker.

This GitHub issue tracker is intended for feature requests in the officially supported builder images only. This issue tracker is not the right place to request features like triggers or notifications.

If you're not sure where to suggest your feature, use Google's public issue tracker.

Detailed Feature Information

Which builder is relevant to this request?
Node / Yarn

Is your feature request related to a problem? Please describe.
Yarn 2 is not currently properly supported by cloud-build:

• Caching is not efficient (every package is fetched at every build)
  
• There are a lot of warnings, like this one:

2021-02-05 10:32:13.866 CET
Step #6 - "builder": ➤ YN0050: The --frozen-lockfile option is deprecated; use --immutable and/or --immutable-cache instead

• Install seems to occur twice, without cache, which makes almost all my builds ending up in timeouts
  

Describe the solution you'd like
Out-of-the-box yarn 2 integration.

Describe alternatives you've considered
currently working on a workaround, will add insights with my progress

Additional context
...

[bendory]

So IIUC, you are asking that a yarn2-compatible builder be added @sylvainar?

[sylvainar]

That would be great indeed, however I'm mostly using Cloud Build to deploy on GAE and I'm not totally sure of the compatibility GAE/yarn2 yet, I can't find any documentation on the web. Maybe that's a bit too soon, anyway I ended up roll backing to yarn1 on my side.

[bendory]

I'm not a yarn user, but it looks to me like it's the same CLI with different options and default settings. Am I misunderstanding?

[sylvainar]

They do indeed, however it seems that we need extra parameters or configuration linked to the issues I posted in the first post.

[bendory]

They do indeed, however it seems that we need extra parameters or configuration linked to the issues I posted in the first post.

Perhaps I'm misunderstanding something (again, I'm not a yarn user) -- is there a reason that you can't pass those extra parameters to your build step as args? Is there a reason you can't submit the required configuration as part of your build?

I'm having trouble understanding what the issue is that you are reporting regarding the existing yarn build step?

[sylvainar]

I'm a beginner in Cloud Build, in fact I only learned recently that having a gcp-build in your package.json while deploying to GAE triggers a Cloud Build job. What I miss is, why does it work so well with yarn1 when it struggles that much with yarn2 ?

I can probably add some parameters to the command but it kinda break the "flawless integration" between GAE and Cloud Build that you have out-of-the-box with yarn1.

[bendory]

I'm closing this as WAI; there is no reported issue here with our existing yarn builder.

Please report App Engine issues using the App Engine Issue Tracker or please escalate your individual issue to your Google Cloud Support representative.