Skip to content

CI: build + deploy to biconomy-infra staging MIG on develop#217

Open
fichiokaku wants to merge 1 commit into
developfrom
feat/biconomy-infra-cicd
Open

CI: build + deploy to biconomy-infra staging MIG on develop#217
fichiokaku wants to merge 1 commit into
developfrom
feat/biconomy-infra-cicd

Conversation

@fichiokaku

Copy link
Copy Markdown
Collaborator

What

New-infra CI/CD pipeline, running in parallel with the existing GKE release flow (which is untouched and stays until GKE decommission).

  • Push to develop → build SHA-pinned image to Artifact Registry (mee-node:<sha> + develop-latest) via WIF (no keys)
  • Then calls the shared reusable deploy workflow in bcnmy/biconomy-infra: creates a SHA-pinned instance template, rolls mee-node-staging-mig, health-gates on https://mee-staging.biconomy.io/v1/info, auto-rolls-back to the previous template on failure, prunes old CI templates
  • deploy/infra-staging/startup.sh is the COS startup script (owned by this repo per the caller-owns-startup convention); image ref comes from instance metadata so every deploy is SHA-pinned

Notes

  • Staging MIG is size 1, rollout_mode=replace → brief blip on deploy (accepted for staging)
  • Prod mee nodes on biconomy-infra stay manually deployed until the GKE cutover; a prod caller with an approval gate follows then
  • warmup 900s: mee-node boot pulls 3 images + 23 chain configs

Parallel to the GKE release flow. Push to develop builds a SHA-pinned
image and rolls mee-node-staging-mig via the shared reusable deploy
workflow (health gate on mee-staging.biconomy.io, auto-rollback).
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.

1 participant