Search…
⌃K

Azure DevOps

Azure DevOps Integration in Avo Assure

Execution using Azure DevOps

  1. 1.
    Log in to Azure DevOps, and navigate to Project settings.
  2. 2.
    Click on the ‘Service Connections’ tab.
Service Connections Screen
3. Click on ‘New Service Connection’. 4. Select the connection type as ‘Generic’ and click on Next. 5. Configuration for the connection should be as below:
  1. 1.
    Server URL: https ://< Avo Assure URL >/ExecuteTestSuite_ICE_SVN.
  2. 2.
    Leave authentication fields empty.
  3. 3.
    Give any service connection name. Example: Avo_Assure_Execution_API.
  4. 4.
    Uncheck ‘Grant access permissions to all pipelines’, if only specific pipelines will use service. If this option is unchecked, then upon running the pipeline with this service for first-time permission has to be granted for usage. (See Steps 6.13, 6.14 below).
  5. 5.
    Click on ‘Save’.
Service Configuration
6. After completing the Service Connection configuration, navigate to CI/CD (Pipelines) configuration file.
7. Search and select the ‘Invoke Rest API’ task from the lists of tasks available on the right-hand side panel.
8. If the tasks panel is not available, click on the ‘Show Assistant’ option available in the top right corner of the editor.
Show Assistant Option to View Task Templates
9. Configuration for the task should look like this:
  1. 1.
    Select Connection Type as Generic.
  2. 2.
    Select the service created in step 5 for the Generic service connection.
  3. 3.
    Set Method as POST.
  4. 4.
    Leave Headers field unchanged.
  5. 5.
    Paste execution request data prepared above in Body.
  6. 6.
    Leave URL suffix and parameters empty.
  7. 7.
    In the Advanced section, select Completion event as ‘Callback’.
  8. 8.
    Click on ‘Add Task’.
Invoke REST API Task Configuration
10. Invoke REST API task is an agentless task. Make sure the Agent pool select for this job is ‘server’.
11. YML snippet looks like below after adding the task.
Invoke REST API Task Configuration
12. Click on ‘Save’ when editing is completed.
13. Before starting the execution, make sure that ICE is connected.
14. If the pipeline has not started with the message permission needed, then that means, ‘Grant access permission to all pipelines’ was not selected while creating the service (see step 5). And this is the first time that the pipeline is triggered using the newly created service. To continue, the execution permission has to be granted.
Approval Request for Using Service Created in Step 5
15. To do so, click on ‘View’ and then ‘Permit’.
16. Once the execution is completed, reports will be generated and can be viewed in the Avo Assure Reports plugin.
17. Depending on the execution status, the task will pass/fail. And depending on additional configuration, the pipeline status will be reflected as pass/fail.