Cloud Build CI/CD für Agenturen: weniger Fehler bei Landingpage-Releases

In einer Webagentur ist oft der letzte Klick vor dem Release einer Kunden-Landingpage der riskante Moment. Eine Preistabelle ändert sich, ein altes Kampagnenbild kommt zurück, eine Test-formId landet in Produktion, ein Werbetag verschwindet oder eine Variable eines anderen Kunden wird genutzt.

Dieser Artikel macht Cloud Build zu einem Release-Ablauf für Agenturen. Claude Code erstellt Checks, Tabellen und cloudbuild.yaml-Entwürfe; Menschen prüfen Kundenzusage, Preise, Rechtstext, Tracking und Produktionszeit.

Kernaussagen

Check client name, URL, form ID, tracking tags, price, legal copy, approver, and rollback before deploy.
Cloud Build gives triggers, approvals, repository connections, service accounts, and build logs.
Claude Code drafts release tables, diff summaries, cloudbuild.yaml changes, and rollback notes.
Humans approve client promises, price, legal copy, tracking, and production timing.
Send serious readers to training because release workflows depend on each agency.

Wo Agentur-Releases scheitern

Der Ablauf startet mit Kunde, öffentlicher URL, Preview-URL, Branch, formId, Tracking, Preisen, Rechtstext, OGP, Freigabe, build id und Rollback. Cloud-Build-Trigger können Repository-Ereignisse nutzen; Freigaben können Builds anhalten. Benutzerdefinierte Servicekonten halten Rechte pro Release-Pfad klein.

Official references: Cloud Build, triggers, approval gates, repositories, user-specified service accounts, and default service account guidance.

Ablauf: Landingpage-Fehler vor Release stoppen

| Area | Draft from Claude Code | Human review |

| --- | --- | --- |

| cloudbuild.yaml | build, test, deploy, rollback | production approver |

| Diff | changed files, price, CTA, tags | client-approved content |

| Env names | required keys, staging/prod difference | no secret values pasted |

| Form | action, formId, thanks URL | production destination |

| Build log | build id, commit, approver, URL | rollback is recorded |

Was Claude Code tut und was Menschen entscheiden

3 Use Cases

Use case 1: Release checklist per client LP

Input: cloudbuild.yaml, package.json, LP diff, preview URL, client approval memo, form settings.
Output: checklist for price, CTA, form ID, tracking tag, OGP, thanks URL, approver.
Human review: confirm client-approved copy, release time, and production contact destination.

Use case 2: Add an approval gate

Input: trigger settings, target branch, release target, approver, emergency rule.
Output: approval conditions, approver, build id, commit, release URL, rejection steps.
Human review: decide whether this client needs approval and whether release timing matches ads.

Use case 3: Split service accounts by client path

Input: Cloud Build service account, Secret references, host target, client project, public URL.
Output: client, service account, readable secrets, deploy target, broad permission candidates.
Human review: confirm client A builds cannot read client B secrets, and retired users are gone.

Kopierbarer Prompt


Review a web agency Cloud Build CI/CD workflow. Goal: reduce client landing page release incidents. Build a release checklist for client name, URL, form ID, tracking tags, price table, approver, and rollback. Separate what Claude Code can inspect, what a human must approve, and what requires client approval. Do not run change commands. Main CTA: /training/.

Prüfcode


const releases = [{ client: 'Client B', url: 'https://example.net/campaign', formId: 'stg-contact', approver: '', rollback: '' }];

const findings = releases.flatMap((r) => {

  const issues = [];

  if (!r.url.startsWith('https://')) issues.push('URL is not HTTPS');

  if (!r.formId || /stg|test|dev/i.test(r.formId)) issues.push('form ID looks like staging');

  if (!r.approver) issues.push('approver is missing');

  if (!r.rollback) issues.push('rollback is missing');

  return issues.map((issue) => ({ client: r.client, issue }));

});

console.table(findings);

if (findings.length) process.exitCode = 1;

Pitfall: CI/CD macht Releases schneller und Unfälle größer

Cause: automation makes the release path fast before the human review path is clear. Fix: let machines check build, links, env names, and form ID format; keep price, legal copy, client approval, and ad timing as human approval steps.

FAQ

Q. Is Cloud Build too heavy for an agency? A. Use it first for high-frequency LPs, forms, and ad-linked releases.

Q. Why not GitHub Actions? A. GitHub Actions can work. Cloud Build is convenient when secrets, hosting, Cloud Run, Cloud Storage, Artifact Registry, and logs are already in Google Cloud.

Q. Can Claude Code deploy directly? A. Start with tables and diffs. Production deploy should wait for human approval.

Mit uns sprechen

ClaudeCodeLab training can help design Cloud Build triggers, approval gates, client-specific service accounts, and rollback notes for an agency release workflow.

Was ich geprüft habe

This article checks frontmatter, official links, three use cases, input-output-human review labels, code fences, and the /training/ CTA. The JavaScript sample detects staging form IDs, missing approvers, and missing rollback steps.