Deployment Tracking

Tests fail at 3:47 PM. Which deployment broke them?

Without a record, you dig through Slack messages. Scroll through CI logs. Ping teammates who are in meetings. 20 minutes gone. The client's waiting on a call. Your PM is refreshing the status page.

It's like debugging with your eyes closed. You know something broke. You just don't know which of the 8 deploys today did it.

Deployment Tracking records every deployment automatically. One line in your CI pipeline: helpmetest deploy myapp. Your dashboard shows a timeline with deployment bars and test failures. The connection is immediate.

How It Works

Copy 📝 
# Basic usage (uses $ENV or defaults to dev, uses git commit as description)
helpmetest deploy api
# With environment
helpmetest deploy api --env production
# With custom description
helpmetest deploy frontend --env staging --description "v1.2.3"
# Preview without creating
helpmetest deploy api --dry-run
# Verbose output
helpmetest deploy api --verbose

What You Get

Gantt chart timeline: Green bars show deployments. Red indicators show test failures. You see which deployment happened right before tests broke.

Environment filtering: Filter by production, staging, or dev. Filter by app name. See deployment frequency.

CI/CD integration: Add one step to your pipeline and deployments appear on the dashboard in seconds.

Copy 📝 
- name: Deploy
  run: kubectl apply -f deployment.yaml
- name: Track deployment
  run: helpmetest deploy $APP_NAME --env production

Quick Start

Copy 📝 
curl -fsSL https://helpmetest.com/install | bash
helpmetest deploy myapp

Check your dashboard. You see the deployment timeline.