This extension is made to serve as an interface between Azure DevOps and Chaos Studio. Users can use this extension as a task for a pipeline, to either Start or Stop an experiment that they have created in Chaos Studio. When Start is selected, the pipeline will wait until the experiment is finished to continue. When Stop is selected, it will finish as soon as the request is received.

How to use

Install the extension within your Enterprise/Organization. This can be done by clicking on the green 'Get it free' button above.

NOTE: This only needs to be done once, unless this extension is later deleted from your organization, whenever the extension is updated it will be updated automatically within your organization.

Prerequisites

• Valid Azure Subscription
• Azure Resource Manager Service connection within Azure DevOps Organization
• Resource Group that houses at least one previously setup Chaos Studio Scenario/Experiment

Adding task to pipeline

After installing the extension, you can now add the task to your pipeline. How to set up yaml for a pipeline is shown below:

- task: AzureChaosStudio.ChaosStudioExtension.custom-build-release-task.Chaos-Studio-Release-Task-Extension@1
  displayName: 'Azure Chaos Studio Extension'
  inputs:
    azureSubscription: <azure subscription>
    resourceGroupName: <name of resource group>
    experimentState: Start # Stop could also be used
    experimentName: <name of the experiment in Chaos Studio>

It can also be setup within Azure DevOps itself, using the following steps:

1. Within a pipeline/release, add a new task, find "Azure Chaos Studio Release Task", and click "Add".
2. Fill in the following fields:
   • Azure subscription: Select the dropdown and find the appropriate subscription.
   • Resource group name: Enter/Select the correct resource group name that the experiment is housed under in Chaos Studio.
   • Experiment State: Select either "Start" or "Stop".
   • Experiment Name: Name of the experiment file that is located within the specified Resource Group.
3. Save these changes.

It should look similar to the following screenshot:

The extension should now run the next time the release pipeline is run.