Skip to content
| Marketplace
Sign in
Azure DevOps>Azure Pipelines>OverOps Azure Extension
OverOps Azure Extension

OverOps Azure Extension

OverOps

|
4 installs
| (0) | Preview
Azure DevOps Extensions for OverOps
Get it free

OverOps Azure DevOps Extension

[ Pre-Release ]

Overview

This extension provides the OverOpsQualityReport task which can be used in the pipeline to generate a QualityReport.
This is report can be used to gage overall quality of the application and fail builds if certain quality gates are not met.

Report

Pipeline Setup

Before getting started familiarize yourslef with how to create Azure DevOps Pipelines (https://docs.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops).

Once the extension is installed you will have access to the OverOpsQualityReport you can use auto complete in the pipeline editor or search for it in the task browser. Once selected you can view all of the valid parameters in the user interface on the right-hand side. Overing over each exclamation mark (!) will give you more details on that parameter.

Example:

Pipeline

Gathering Data

Before we can create a quality report the application or automated tests need to be run in a seperate task with the OverOps agent attached. The OverOps agent is the entity that captures events and provides the necessary data to generate the quality report. For more information on how to run and attach visit one of the following links:

  • Java - https://doc.overops.com/docs/overops-for-java
  • .Net - https://doc.overops.com/docs/introduction-to-dotnet-microagent

Parameters

In the above pipeline you will see the parameters block. This is how you can parameterize the build so that users override default behavior of the build. In this example we give them the ability to mark the build stable even if quality gates to not pass. This may be useful to force a build pipeline for further investigation. Other parameters can be created depending on how you want to manage the inputs.

Run

Pipeline Setup

In the above pipeline you waill see the variables block. Because each pipeline is checked into source control and can viewed by all maintainers and/or community (if open source) we want to protect certain variables. It is considered best practice to leverage variable groups for things like the API Key & SID. Other variables can be created depending on how you want to manage the inputs.

Variables

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft