From 8bea7d88ae9bae1bff5fcc9709f391662d748541 Mon Sep 17 00:00:00 2001 From: Zoltan Kochan Date: Sat, 8 Aug 2026 21:59:40 +0200 Subject: [PATCH] ci: restore --keep-lane in bit_pr The GVS PR dropped --keep-lane to dodge the lane-reuse artifact mixing tracked in #10583. Restore lane reuse so a PR keeps one lane on Bit Cloud and each push re-snaps only what changed; the comment now records the hazard and how to recognize it instead of the workaround. Co-Authored-By: Claude Opus 5 (1M context) --- .circleci/config.yml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 272dacc8409c..0214fbccffa2 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -856,13 +856,14 @@ jobs: # NOTE: PR builds run the FULL pipeline by default. To trade specific tasks for speed on a # given PR (no YAML change needed), add a `[skip-tasks: ]` token to the commit # message, e.g. `[skip-tasks: ExtractSchema,GeneratePreview,GenerateEnvTemplate,PublishComponents]`. - # No --keep-lane: the reusing flow serves components unchanged since an earlier export - # from the lane, with artifacts built from older commits of the branch. Capsules then mix - # generations of @teambit packages and cross-copy `instanceof` breaks in capsule spec - # runs - on a PR that snaps core components (so their specs actually run), bit_pr fails - # deterministically from the second push onward. The temp-lane flow rebuilds every run - # from one commit, trading the lane's persistent history on Bit Cloud for correctness. - command: 'cd bit && bit ci pr --build --skip-cleanup' + # --keep-lane: reuse the lane named after the branch across pushes, so the PR keeps one + # lane on Bit Cloud and pushes only re-snap what actually changed. Known hazard while + # #10583 is open: the reusing flow serves components unchanged since an earlier export + # with artifacts built from older commits, so capsules can mix generations of @teambit + # packages and cross-copy `instanceof` breaks in capsule spec runs. If a PR that snaps + # core components starts failing from the second push onward, that is this - rename the + # branch (fresh lane) or drop --keep-lane on that PR. + command: 'cd bit && bit ci pr --build --keep-lane --skip-cleanup' no_output_timeout: '50m' environment: NODE_OPTIONS: --max-old-space-size=30000