Example
An example of adding a PipeRider report to your CI workflow
Last updated
An example of adding a PipeRider report to your CI workflow
Last updated
The concept of using PipeRider with your CI process is based on PR (pull request) review.
The following CI examples use dbt's Jaffle Shop project to demonstrate how PipeRider can integrate with your CI process.
To better understand the changes to the data pipeline when a pull request is created, you can follow these steps to automatically transform your model changes, profile the data source, and compare the changes between the pull request and main branches.
The pipeRider compare feature provides a way to compare two runs based on a pre-defined recipe file. The default recipe file should be located at .piperider/compare/default.yml
The PipeRider compare command will be based on the pre-defined recipe file to compare your PR and main branches.
The compare feature outputs a Markdown-formatted comparison summary that you can attach to your pull request comment or upload to your own storage.
The PipeRider Compare Action is a GitHub Action that executes compare command appends PR comments, and uploads the result to the artifacts.
Upload the Markdown file and the comparison report to your own storage using your own script, if required.