Skip to content
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
Closed
3 tasks done
Tracked by #7571
Assignees
Labels
enhancement New feature or request

Comments

@emmyoop
Copy link
Member

emmyoop commented Mar 29, 2024

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

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 the release.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.

@emmyoop emmyoop added the enhancement New feature or request label Mar 29, 2024
@emmyoop emmyoop mentioned this issue Mar 29, 2024
3 tasks
@emmyoop emmyoop self-assigned this Mar 29, 2024
@emmyoop emmyoop reopened this Mar 29, 2024
@emmyoop emmyoop reopened this Apr 5, 2024
@mikealfare mikealfare reopened this Apr 15, 2024
@mikealfare mikealfare reopened this Apr 15, 2024
@mikealfare mikealfare linked a pull request May 14, 2024 that will close this issue
3 tasks
@mikealfare mikealfare reopened this May 15, 2024
@mikealfare mikealfare reopened this May 20, 2024
@mikealfare mikealfare reopened this May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment