Badgr Agent CI for Azure DevOps

Badgr Agent CI diagnoses why your Azure Pipelines fail and posts the likely cause, evidence, and suggested fix to your pull request thread or build summary.

Part of the Badgr Agent product family from AI Badgr.

What it does

• Fetches real logs from the failed pipeline task
• Diagnoses common failures (tests, installs, TypeScript, Docker, permissions, env vars, timeouts)
• Posts one deduped comment on reruns — no spam
• Shows quoted evidence from your logs
• Suggests concrete next steps with a confidence score
• Falls back to the build summary when no PR is available

What it does not do

• Does not auto-fix or modify your code
• Does not rerun pipelines or open/merge PRs
• Does not require changes to your existing tests

Quick start

1. Get an API key

Sign up at aibadgr.com and copy your BADGR_API_KEY.

2. Add a pipeline variable

1. Pipelines → Library → Variable groups (or pipeline variables)
2. Add secret variable: BADGR_API_KEY
3. Enable Allow scripts to access the OAuth token in pipeline settings (for System.AccessToken)

3. Add the task to your YAML

steps:
  - script: npm test
    displayName: Run tests

  - task: BadgrCI@1
    displayName: Badgr Agent CI
    condition: failed()
    env:
      BADGR_API_KEY: $(BADGR_API_KEY)
      SYSTEM_ACCESSTOKEN: $(System.AccessToken)

Run your pipeline. When a step fails, Badgr Agent CI posts a diagnosis within about 30 seconds.

Example diagnosis

### Badgr Agent CI

**Likely cause:** Missing dependency `vite`

**Evidence:**
- Cannot find module 'vite'
- Failed during `npm test`

**Suggested fix:** Add to devDependencies: `npm install --save-dev vite`

**Confidence:** high

Requirements

• Azure DevOps Services or Azure DevOps Server
• BADGR_API_KEY from AI Badgr
• OAuth token access enabled for pipeline scripts

Support

• Documentation: github.com/michaelmanly/gpu-ai
• Email: hello@aibadgr.com

License

Apache-2.0