Skip to content

Wipe node out on toolchain change - #134

Merged
Andarist merged 2 commits into
masterfrom
wipe-node-out-on-toolchain-change
Sep 21, 2026
Merged

Andarist merged 2 commits into
masterfrom
wipe-node-out-on-toolchain-change

Conversation

@Andarist

Copy link
Copy Markdown
Member

extracted from #132

Andarist and others added 2 commits September 21, 2026 07:36
The build step mounts a per-agent cache of the node checkout and its out/
directory so make can rebuild incrementally, but the builder image is built
from the Dockerfile at the pinned backend rev (REPLAY_BACKEND_REV), which
is currently ubuntu 20.04 / g++ 9 while backend master is on 22.04 / g++ 11.
Once objects from one toolchain land in an agent's cache, a job using the
other fails to link them: g++ 11 emits references to
std::__throw_bad_array_new_length (GLIBCXX_3.4.29), which 20.04's libstdc++
does not have, so gen-regexp-special-case dies with an undefined reference
that has nothing to do with the commit being built.

Stamp the image's g++ version next to the objects and wipe out/ when it
changes, trading a cold rebuild for an unexplainable link failure.
Stamping the compiler version only prevented the next mismatch: an agent
whose cache already holds objects from another toolchain has no stamp, so
nothing was wiped and the first build still failed on the undefined
GLIBCXX symbol. Treat a missing stamp as unknown objects and wipe those
too, so the agents currently in that state heal themselves.

Key on the FROM line of the pinned Dockerfile instead of running g++ in
the image: it reads the source of truth without a docker run, and a pin
bump that leaves the base image alone no longer forces a cold rebuild.

Co-Authored-By: D. Seifert <Domiii@users.noreply.github.com>
@Andarist
Andarist merged commit a4011bf into master Sep 21, 2026
2 of 3 checks passed
Andarist added a commit that referenced this pull request Nov 6, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist added a commit that referenced this pull request Nov 6, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist added a commit that referenced this pull request Nov 6, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist added a commit that referenced this pull request Nov 6, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 10, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist pushed a commit that referenced this pull request Nov 11, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist added a commit that referenced this pull request Nov 11, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist added a commit that referenced this pull request Nov 11, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Andarist added a commit that referenced this pull request Nov 12, 2026
Add build/test, release, and branch-test workflows, along with
approveman and SOC2 compliance config for the Replay fork. Add the
Buildkite pipeline (.buildkite/runtime-node-build-and-test.yml) that
builds node and runs the backend test suites against it, and
replay_build_scripts/build-pipeline.py, which pins REPLAY_BACKEND_REV
into the pipeline for `buildkite-agent pipeline upload`. The GitHub
build-test workflow is kept for manual dispatch only.

The test steps call the backend's buildNode.ts suites under the names
it uses now: the node test step runs test-node-core only, no longer
the test/node-recording suite as well, and the jest step runs
test-jest-repos.

Rebase note: the pipeline's step names have to follow the backend's
buildNode.ts subcommands (test-node-recording, test-node-core,
test-jest-repos); a suite renamed there fails the step until the
pipeline follows. Every backend revision the pipeline triggers, clones
or tests against comes from REPLAY_BACKEND_REV through
build-pipeline.py's __REPLAY_BACKEND_REV__ placeholders, never a
hard-coded sha.

Includes later changes from #127, #128, #132, #134, #154 and #156.

Co-authored-by: Domi <Domiii@users.noreply.github.com>
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Co-authored-by: Gideon Redelinghuys <gideon@replay.io>
Co-authored-by: Dan Miller <dan@replay.io>
Co-authored-by: Holger Benl <hbenl@evandor.de>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant