-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Automate Docker Release #109
Closed
3 tasks done
Tracked by
#7571
emmyoop opened this issue
Mar 29, 2024
· 0 comments
· Fixed by #108, dbt-labs/dbt-core#9833, dbt-labs/dbt-snowflake#963, dbt-labs/dbt-redshift#758 or dbt-labs/dbt-bigquery#1170
Closed
3 tasks done
Tracked by
#7571
[Feature] Automate Docker Release #109
emmyoop opened this issue
Mar 29, 2024
· 0 comments
· Fixed by #108, dbt-labs/dbt-core#9833, dbt-labs/dbt-snowflake#963, dbt-labs/dbt-redshift#758 or dbt-labs/dbt-bigquery#1170
Labels
enhancement
New feature or request
Comments
5 tasks
This was
linked to
pull requests
Apr 10, 2024
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this your first time submitting a feature request?
Describe the feature
The Docker release is currently done manually and we often drop getting it out the door: dbt-labs/dbt-core#7571. We already have a workflow to complete the process. let's add a workflow_call step, move it from
dbt-core
to this repo and then add calls in therelease.yml
in each repository to trigger releasing the docker image at the same time we release to github and pypi.Describe alternatives you've considered
Continue to manually trigger the docker release
Who will this benefit?
Consumers of our docker images
Are you interested in contributing this feature?
No response
Anything else?
<= v1.7 dbt-postgres and dbt-core are released together. After that each package will be separate.
Keep the workflow_dispatch trigger to we can continue to trigger manually when needed.
The text was updated successfully, but these errors were encountered: