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

CI: push images to ACR #1285

Merged
merged 2 commits into from
Feb 26, 2025
Merged

CI: push images to ACR #1285

merged 2 commits into from
Feb 26, 2025

Conversation

bayandin
Copy link
Member

@bayandin bayandin commented Feb 25, 2025

This PR begins pushing images to ACR (along with ECR) for releases.

  • Added .github/workflows/_push-to-acr.yaml workflow to push images to ACR (copied from cloud repo)
  • Renamed inputs.upload-to-ecr to inputs.upload-to-ecr-acr

@bayandin bayandin force-pushed the bayandin/acr branch 2 times, most recently from 5427741 to e2afa01 Compare February 25, 2025 22:53
@bayandin bayandin marked this pull request as ready for review February 25, 2025 23:12
@mikhail-sakhnov
Copy link
Contributor

lgtm to me. We might probably want to do the ECR uploading as a separate workflow.

@bayandin
Copy link
Member Author

bayandin commented Feb 26, 2025

lgtm to me. We might probably want to do the ECR uploading as a separate workflow.

Eventually, we're going to use a workflow like this from neon repo to push images.
So, at this point, I wouldn't want to change anything too excessive for autoscaling.

@bayandin bayandin enabled auto-merge (squash) February 26, 2025 19:02
@bayandin bayandin merged commit 8101bab into main Feb 26, 2025
35 checks passed
@bayandin bayandin deleted the bayandin/acr branch February 26, 2025 19:23
jcgruenhage added a commit that referenced this pull request Mar 10, 2025
jcgruenhage added a commit that referenced this pull request Mar 10, 2025
This reverts commit 8101bab.

The reason for this is a release build failing, see
https://github.com/neondatabase/autoscaling/actions/runs/13726698604/job/38434423513.
I'll look into re-applying this fix again after the release is cut and
fixing the underlying problem.
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.

2 participants