Knowledgebase

Deploying to Google Cloud Print

  • googletechnology, google, migration, woocommerce, errors, guide, howto, solution
  • 0

Getting applications running.

WHAT DEPLOYMENT APPROACHES EXIST

Building and deploying from a pipeline Deploying a container image Source-based deployment, where the platform builds for you

WHAT TO PREFER

A pipeline producing an artefact, deployed automatically.

WHY

Reproducible, reviewable, and not dependent on anyone's machine.

WHAT CLOUD BUILD PROVIDES

Building, testing and deploying, triggered by repository changes.

WHAT TO STORE IMAGES IN

The artefact registry, with versioned tags.

WHAT TO NEVER USE

A tag that moves, such as latest, for production deployments.

WHY

You cannot establish what is actually running, or roll back reliably.

WHAT TO CONFIGURE

Environment values outside the image Secrets from the secret manager, not environment variables in configuration

WHAT TO USE FOR SAFE RELEASE

Gradual traffic migration between revisions.

WHAT THAT PROVIDES

Sending a small proportion of traffic to a new version, and reverting instantly.

WHAT TO VERIFY AFTER DEPLOYING

The service responds Logs are clean Error rate is unchanged

WHAT TO KEEP

The previous revision, for reversal.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot