Skip to content

Latest commit

 

History

History
44 lines (23 loc) · 2.03 KB

DEPLOYMENT.md

File metadata and controls

44 lines (23 loc) · 2.03 KB

Steps to deploy abstractions to production

These steps are for Dune employees. If you are a wizard, reach out to a Data Experience team member.

After you have merged your code into master. (Soon to be updated to main)

git checkout master

Double check you have all the latest changes

git pull --rebase

Create an annotated tag using semantic versioning. See the Releases page to check the previous version.

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible changes,
  2. MINOR version when you add functionality in a backwards compatible manner, and
  3. PATCH version when you make backwards compatible bug fixes.

git tag -a vX-X-X -m "some notes on the changes"

Push your tag to github

git push origin vX-X-X

Navigate to the Releases page for the repo. Click create a release.

Screen Shot 2022-05-27 at 2 44 14 PM

From the release creation page, use the drop down menu to select your tag. Write some notes to describe the changes since last release.

Screen Shot 2022-05-27 at 2 44 25 PM

Update the branch name on the production environment on DBT Cloud.

Screen Shot 2022-05-31 at 9 46 24 AM

To deploy the new version, run the "Manually Deploy New Version" job in the Production environment in dbt Cloud. This will ensure models and tests are updated.

Rollback

Check the Releases page and deploy the previous tag to DBT Cloud.