-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[yarn] download prebuilt artifacts for re2 and node-sass from custom mirrors #126820
Conversation
53c17da
to
802d511
Compare
Pinging @elastic/kibana-operations (Team:Operations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
…mirrors (elastic#126820) Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit c509fda) # Conflicts: # yarn.lock
…ustom mirrors (#126820) (#126855) * [yarn] download prebuilt artifacts for re2 and node-sass from custom mirrors (#126820) Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit c509fda) # Conflicts: # yarn.lock * update kbn/pm dist
Rather than run build scripts on M1 Mac machines to take care of missing native packages for
node-sass
andre2
packages, we publish our own builds of these modules that we will download during yarn-install via custom mirrors and environment variables which customize the post-install scripts. This will ensure that everyone has the same artifacts and therefore can utilize the bazel remote cache.To do this we need to publish all the build artifacts for each version to a bucket, along with the artifact for the darwin-arm64 build. This means we won't be able to update Node or these two packages without pushing up new artifacts, but hopefully this will be a very short lived thing until the upstream repos can start publishing M1 compatible artifacts.