gcb-monitor

# Google Cloud Build Monitor

Monitor, analyze, and diagnose Google Cloud Build executions using the gcloud CLI. Provide continuous status updates until builds complete, with detailed failure analysis when builds fail.

## Prerequisites

Ensure the gcloud CLI is installed and authenticated:

```bash
gcloud auth list
gcloud config get-value project
```

If not authenticated, inform the user and provide authentication guidance.

## Core Workflow

### Step 1: Identify the GCP Project

Determine which GCP project contains the build:

1. Check current default project:
   ```bash
   gcloud config get-value project
   ```

2. If context suggests a specific environment (staging, production, dev), look for matching projects:
   ```bash
   gcloud projects list --format="table(projectId,name)" --filter="projectId~staging OR name~staging"
   ```

3. If multiple projects exist and the correct one is unclear, list available projects and ask the user:
   ```bash
   gcloud projects list --format="table(projectId,name)"
   ```

4. Context clues for project selection:
   - Branch name "staging" or "main" → look for staging/production projects
   - Recent merge to main → likely production build
   - PR context → likely staging or CI project

### Step 2: Find the Build

Locate the specific build to monitor:

**List recent builds:**
```bash
gcloud builds list --project=PROJECT_ID --limit=10 --format="table(id,status,createTime,source.repoSource.branchName,substitutions.TRIGGER_NAME)"
```

**Find in-progress builds:**
```bash
gcloud builds list --project=PROJECT_ID --filter="status=WORKING OR status=QUEUED" --format="table(id,status,createTime,source.repoSource.branchName)"
```

**Find builds by branch:**
```bash
gcloud builds list --project=PROJECT_ID --filter="source.repoSource.branchName=BRANCH_NAME" --limit=5
```

**Build identification strategy:**
1. If user specifies build ID → use that directly
2. If user mentions "latest" or "current" → find most recent or in-progress build
3. If