From ae6cf8c366fabd15c05add47173387ee419338d4 Mon Sep 17 00:00:00 2001 From: Michael Smith Date: Mon, 19 May 2025 12:18:14 -0400 Subject: [PATCH] fix: add build step for deployment registry (#110) ## Changes made - Updated the `deploy-registry` script to include steps for pushing to the production registry --- .github/workflows/deploy-registry.yaml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/.github/workflows/deploy-registry.yaml b/.github/workflows/deploy-registry.yaml index cce36ee3..ac3e9d6e 100644 --- a/.github/workflows/deploy-registry.yaml +++ b/.github/workflows/deploy-registry.yaml @@ -28,9 +28,8 @@ jobs: service_account: registry-v2-github@coder-registry-1.iam.gserviceaccount.com - name: Set up Google Cloud SDK uses: google-github-actions/setup-gcloud@77e7a554d41e2ee56fc945c52dfd3f33d12def9a - # For the time being, let's have the first couple merges to main in - # modules deploy a new version to *dev*. Once we review and make sure - # everything's working, we can deploy a new version to *main*. Maybe in - # the future we could automate this based on the result of E2E tests. - name: Deploy to dev.registry.coder.com run: gcloud builds triggers run 29818181-126d-4f8a-a937-f228b27d3d34 --branch dev + - name: Deploy to registry.coder.com + run: | + gcloud builds triggers run 106610ff-41fb-4bd0-90a2-7643583fb9c0 --branch main