Repository navigation
Conversation
tnazarew
force-pushed
the
local-runs/dbt
branch
from
November 12, 2026 11:34
45d6960 to
ca6ccfc
Compare
tnazarew
force-pushed
the
dev/shared-helpers
branch
from
November 12, 2026 13:16
a103d71 to
4ad9797
Compare
tnazarew
force-pushed
the
local-runs/dbt
branch
2 times, most recently
from
November 13, 2026 19:13
82c2500 to
4b1d51b
Compare
- producer/dbt/runner/run_scenarios.sh runs the scenarios and records how each ended in status.json (dev/lib/status.sh). The CI run step now calls it instead of inline YAML; a failed scenario is recorded, not a failed step. - producer/dbt/run_dbt_tests.sh is rewritten as a plain local run with the same steps as CI: a cached virtualenv with dbt-core==V, dbt-postgres and openlineage-dbt==OL, the scenarios valid for the versions, run_scenarios.sh, and dev/validation/validate_locally.sh. It no longer needs an OpenLineage checkout or hardcodes dbt 1.8.0. - README: "Run locally, as CI does", with the one command, the same steps by hand (one per CI step) and how to read the output. The template producer gets the same script shape and a README skeleton; producer/README.md lists the command. - .gitignore: the local run's default output in the repo root. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: tnazarew <tomasz.nazarewicz@getindata.com>
tnazarew
force-pushed
the
dev/shared-helpers
branch
from
November 16, 2026 11:39
b986c9a to
ba67c60
Compare
tnazarew
force-pushed
the
local-runs/dbt
branch
from
November 16, 2026 11:39
4b1d51b to
6190754
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #356 (
dev/helpers). Part of the robustness work: contributors should be able to test a scenario on their machine before committing, with the same steps and scripts as CI.Why
producer/dbt/run_dbt_tests.shdidn't do what CI does. It needed a local OpenLineage checkout, validated every run as dbt1.8.0(hardcoded), ran every scenario regardless of version, and installed packages into whatever environment was active. The CI run loop was inline YAML, so nothing could share it.What
producer/dbt/runner/run_scenarios.sh --events-dir DIR --scenarios 's1;s2'runs each scenario'stest/run.shand recordsDONE/FAILEDinstatus.jsonwithdev/lib/status.sh. A failed scenario doesn't stop the others and doesn't fail the script; validation fails it with a "producer job" test (validation: report checks that didn't run instead of passing them #353). CI's run step is now this one call. It no longer hascontinue-on-error, so only an infrastructure error (for example, a missingjq) fails the step.producer/dbt/run_dbt_tests.sh --component-version V --openlineage-version OL [--scenarios] [--events-dir] [--report-dir]is plain and linear, with the CI steps in order:scripts/get_valid_test_scenarios.sh)run_scenarios.shdev/validation/validate_locally.sh, which writesdbt-V-OL-report.json(the CI artifact name) and exits 1 if a scenario failedproducer/dbt/README.md"Run locally, as CI does" covers prerequisites, picking versions, the one command, the same steps by hand (one command per CI step, labelled with its name), where the output lands, how to read a failure, and how to stop the Postgres container.run_template_tests.shhas the same shape with TODOs, andREADME.mdis a skeleton of the sections.producer/README.mdlists the dbt command..gitignore: the default output (/*-events-*/,/*-report.json) when run from the repo root.Verification
pytest scripts/tests: 87 passed. The new scripts'--help, unknown option and missing arguments are covered bytest_run_scripts.py.run_dbt_tests.sh --component-version 1.8.0 --openlineage-version 1.55.0(Python 3.12, like CI) with Docker stubbed to fail:csv_to_postgreswas picked and recorded asFAILED🤖 Generated with Claude Code