Skip to content

ci: use reusable workflows from dbt-labs/dbt-package-testing@v2#574

Merged
b-per merged 3 commits into
mainfrom
ci/use-dbt-package-testing-reusable-workflows
Apr 21, 2026
Merged

ci: use reusable workflows from dbt-labs/dbt-package-testing@v2#574
b-per merged 3 commits into
mainfrom
ci/use-dbt-package-testing-reusable-workflows

Conversation

@b-per
Copy link
Copy Markdown
Collaborator

@b-per b-per commented Apr 20, 2026

Summary

  • Replace inline integration-test jobs in ci.yml and fusion.yml with calls to the reusable workflows run_tox.yml@v2 and run_tox_fusion.yml@v2 from dbt-labs/dbt-package-testing.
  • Preserve the existing schema naming (dbt_project_evaluator_integration_tests_snowflake_..., dpe_integration_tests_bigquery_..., etc.) and secret mappings (SNOWFLAKE_PASSDBT_ENV_SECRET_SNOWFLAKE_PASS, REDSHIFT_PASSDBT_ENV_SECRET_REDSHIFT_PASS).
  • Keep the standalone run-duckdb-tests Fusion job as a quick credential-free check that gates the cloud Fusion job.
  • Keep pull_request_target + cloud-tests environment gating for fork PRs and PR-head checkout behavior.

The project previously referenced this reusable workflow but it was not functioning (couldn't use pull_request_target); the upstream reusable workflow has since been updated to support that trigger.

Test plan

  • Core integration tests pass for snowflake, bigquery, redshift, databricks
  • Fusion duckdb job runs without cloud credentials
  • Fusion snowflake cloud job runs after duckdb job succeeds
  • Fork PR triggers cloud-tests environment approval gate

Switch ci.yml and fusion.yml to call the shared reusable workflows
(run_tox.yml and run_tox_fusion.yml) instead of inlining the matrix,
checkout, and tox setup steps. Preserves existing schema names,
secret mappings, and the pull_request_target fork-PR environment gate.
@b-per b-per requested review from a team, dave-connors-3 and graciegoheen as code owners April 20, 2026 19:06
b-per added 2 commits April 20, 2026 21:17
Fusion mis-resolves the path to the package's `dbt_project_evaluator_exceptions`
seed when running `dbt seed` from a consuming project, producing a doubled
`dbt_packages/dbt_project_evaluator/dbt_packages/dbt_project_evaluator/seeds/...`
prefix and failing with an IO error.

The seed isn't required here: integration_tests_2 only runs `dbt run`
(not `dbt build`), so the on-run-end filter macro that reads the exceptions
seed is never invoked.
The SL migration added a date_day time dimension to dim_model_7's YAML
but never projected the column in the SQL and never set its data_type.
Fusion's strict contract check fails on both counts. Emit a date literal
as date_day in the SELECT and declare `data_type: date` in the YAML.
@b-per b-per merged commit 057b537 into main Apr 21, 2026
10 checks passed
@b-per b-per deleted the ci/use-dbt-package-testing-reusable-workflows branch April 21, 2026 07:19
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