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

Update github action versions and change cr3 extract to build on master #1251

Merged
merged 1 commit into from
Jul 14, 2023

Conversation

chiaberry
Copy link
Member

@chiaberry chiaberry commented Jul 14, 2023

Associated issues

none

The multi architecture image tagged production didn't build because it only builds when the production branch is updated. I changed the workflow to build the production tag when the code is merged to master for the cr3 narrative docker image but didn't touch the other two so Frank could give his input on whether or not those should wait for production releases.


Ship list

  • Code reviewed
  • Product manager approved

Copy link
Contributor

@mddilley mddilley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense to me and aligns with our release to production approach for ETLs to me. 🚀

@chiaberry chiaberry merged commit d27e0d2 into master Jul 14, 2023
9 checks passed
@johnclary
Copy link
Member

nice!

Copy link
Member

@frankhereford frankhereford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you Chia!

tags: atddocker/atd-vz-cr3-extract:${{ github.ref == 'refs/heads/production' && 'production' || 'latest' }}
tags: atddocker/atd-vz-cr3-extract:${{ github.ref == 'refs/heads/master' && 'production' || 'latest' }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had waffled on this back and forth heavily, before we had really started to get experience porting and adding DAGs. There's even a post it note on my monitor at home to ask y'all what you thought! I couldn't decide if we wanted to tie our images to release VZ Suite release events or if they should float to whenever we push changes on the main branch.

I am really glad you caught this. This is great, thank you!

@chiaberry chiaberry deleted the chia-update-github-workflow branch August 29, 2023 15:33
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.

4 participants