Hi Zoran, > On Oct 26, 2021, at 12:58 AM, Zoran Regvart <zo...@regvart.com> wrote: > > Hi David, > > On Mon, Oct 25, 2021 at 5:07 PM David Jencks <david.a.jen...@gmail.com> wrote: >> The promise of pnp seems to be only partially fulfilled. If I run yarn >> build-all on a clean checkout, it fails because the stuff in >> antora-ui-camel/.yarn/unplugged is for linux, not macOS. I have to run yarn >> workspaces foreach rebuild in order to get a working build. I’m going to >> add this to the Jenckinsfile so if I check in depedency updates it won’t >> break the jenkins build. > > It does look to me like the cache was platform-dependent, I think it's > also Node/Gyp/C++/linker tooling dependent, I did run into that on > #646[1], not sure what the best option is. I'm a bit scared that > without proper cache check we'll end up getting into all sorts of > issues. >
I think .yarn/cache is unmodified but .yarn/unplugged changes on these rebuilds. I think it’s more important that everyone can check in changes to the dependencies than these warnings disappear. If you can find a way to get the checked in .yarn/unplugged to match the Jenkins environment, great, as long as we keep the rebuild-all script for people on other platforms :-) If the Jenkins and GitHub environments are sufficiently similar, perhaps the regen bot or something like it could produce a PR with the rebuild changes. David Jencks
