Revetly
Manual 0.8.0

Connect an Azure DevOps team project

Point one project at a team project in Azure DevOps, so CONTEXT reads its work items. The scope is named in the file, and its token is named in the environment.

Before you start

Configuration page

  1. Open the configuration page. If it is not open, run revetly config and open the address it prints.

  2. On the project's card, select Add source.

  3. Choose Azure DevOps.

  4. Enter the organization in Azure DevOps organization.

  5. Enter the team project in Team project. Revetly reads the whole team project until an area path or a saved query narrows it.

  6. Enter the token in Key for the azure-devops connector. Leave the variable-name box above it alone.

  7. Select Save.

    You should see Access token: set on the card.

  8. On the same line, read the team project the card says it reads.

    You should see Azure DevOps: <ORGANIZATION> / <TEAM_PROJECT> on the card.

  9. Select Test connection on the Azure DevOps line. Revetly answers with what it reached, and puts any advice after it.

    You should see https://dev.azure.com/<ORGANIZATION> answers and project '<TEAM_PROJECT>' resolves on the card.

Command line

  1. In revetly.toml at the project root, add Azure DevOps to what this project reads:

    # revetly.toml
[connectors]
enabled = ["pm", "docs", "conversations", "deliveries", "azure-devops"]

    Revetly replaces this list rather than merging into it, so it restates every source already read.

  2. In revetly.toml, name the organization and the team project in one table:

    # revetly.toml
[connectors.azure-devops]
organization = "contoso"
project = "Platform"

    Replace both values with the organization and team project your work items are in.

  3. Read back the scope this instance will read:

    revetly doctor --offline

    [PASS] azure-devops: settings organization = '<ORGANIZATION>', project = '<TEAM_PROJECT>'

  4. Read which variable the token is read from:

    revetly check

    connector 'azure-devops': AZURE_DEVOPS_PAT is not set in the environment — …

  5. In .env beside it, put the token that line named: 

    # .env
AZURE_DEVOPS_PAT=<AZURE_DEVOPS_TOKEN>

    Replace <AZURE_DEVOPS_TOKEN> with a personal access token that may read work items.

  6. Test the connection to Azure DevOps: 

    revetly doctor

    [PASS] azure-devops: reachable  https://dev.azure.com/<ORGANIZATION> answers and project '<TEAM_PROJECT>' resolves

Troubleshooting

Next steps