AzentAzent

Validation Pipeline

A validation pipeline lets Azent verify its own changes before opening a pull request. If the pipeline fails, the agent reads the logs, fixes the issues, and retries — producing higher quality code with fewer review cycles.

How it works

  1. The agent implements the requested changes and pushes a commit
  2. If ValidationPipelineId is set in .azent.json, the agent triggers that Azure Pipeline on the current branch
  3. The agent waits for the pipeline to complete
  4. If the pipeline succeeds, the agent proceeds to open or update the pull request
  5. If the pipeline fails, the agent reads the build logs, diagnoses the issue, applies a fix, pushes again, and re-runs the pipeline
  6. This loop continues until the pipeline passes or the agent determines it cannot resolve the issue

Setup

  1. Create an Azure Pipeline in your project that runs your build/test/lint steps (e.g. dotnet build, npm test, eslint)
  2. Note the pipeline's numeric ID (visible in the URL when you open the pipeline in Azure DevOps)
  3. Add it to your repository's .azent.json:

{

"ValidationPipelineId": 42

}

Recommendations

  • •Keep the validation pipeline fast (under 5 minutes). Long pipelines increase agent runtime and cost.
  • •Include the checks that matter most: compilation, unit tests, and linting are good defaults
  • •Ensure the pipeline YAML triggers on all branches so it can run on agent-created branches
  • •Make sure the bot user has Build (Read & Execute) PAT scope