chore(NA): downgrades rules nodejs into v4.7.0#130347
Conversation
There was a problem hiding this comment.
LGTM, yarn kbn reset && yarn kbn bootstrap with a populated remote cache took 64 seconds.
info [bazel] INFO: Elapsed time: 64.299s, Critical Path: 8.51s
info [bazel] INFO: 945 processes: 658 remote cache hit, 280 internal, 7 darwin-sandbox.
info [bazel] INFO: Streaming build results to: https://app.buildbuddy.io/invocation/a5358f3e-22ff-492e-9f79-4bb33c1ae960
60mb downloaded, pretty reasonable (a couple cache misses on ARM macs are expected, but not causing any issues right now).
|
Pinging @elastic/kibana-operations (Team:Operations) |
💚 Build SucceededMetrics [docs]
To update your PR or re-run it, just comment with: |
jbudz
left a comment
There was a problem hiding this comment.
Windows LGTM. Uncached reset took 15 minutes and 35 seconds. I'm thinking it's probably worth adding cache hits to CI metrics to unskew bootstrap times.
* chore(NA): downgrade rules nodejs into v4.0.0 * chore(NA): include windows patch * chore(NA): polish downgrade code * chore(NA): include yarn.lock (cherry picked from commit 0b2da10)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
* chore(NA): downgrade rules nodejs into v4.0.0 * chore(NA): include windows patch * chore(NA): polish downgrade code * chore(NA): include yarn.lock (cherry picked from commit 0b2da10) Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
|
For awareness, we've had to add a |

This PR reverts what was done at #129522 , #130051 and #130214 as we found a major performance decreasing when building without no cache.