Redocly is integrated with Azure Repos (which is part of Azure DevOps). You can trigger workflows in Redocly automatically when you commit or open a pull request.
Azure Repos connection requires an enterprise-level Redocly plan.
Redocly integrates by using a personal access token to authenticate to Azure Repos.
We recommend using a service user account. A service user is a user created in Azure Repos intended for use by a machine. You would login to the service user account to generate a personal access token for use by a 3rd party service (like Redocly). We recommend naming your service user "Redocly" or similar.
- Create a personal access token
You must define the scopes correctly.
Set permissions for the personal access token.
custom defined scopes.
read & writecode access
- Set Web/Service hooks permissions
Read the Azure docs to learn how to create a personal access token. Azure DevOps has a current and preview features environment which have different locations for finding where to generate your personal access token.
If you set an expiration on the personal access token, set yourself a reminder to generate a new token.
- Navigate to the Org Settings > Source control providers page.
- Scroll down to the Azure settings section of the page, and fill the form. Enter the Organization name as it appears in your Azure account. Then, enter your personal access token that you created there. Select to Save Azure Settings.
You can update your token by selecting Change, changing your token, and then selecting Update Azure Settings.
You've connected Azure Repos to Redocly.
You will be able to create a new project and select Azure as your source.
Then click Next*- to continue to the next screen, where you select your **Repository.
Once you selected, you can select your production branch. We also recommend to select the *Build PR as previews- which will trigger workflows to build a preview of your docs.
Finally, you will give your project a name.
This section provides a follow-along demo of using the Azure Repos connection.
- An Azure Repo with a valid OpenAPI definition or Developer Portal.
- A project, configured with the *Build PR as previews- as described above.
- Git knowledge.
- Clone your repo, if you haven't already.
- Create a branch, and make a minor change.
- Commit and push to the Azure Repos origin.
- Open a pull request.
- Check the Project overview screen or the Project builds screen. A preview build should be triggered.
- Upon completion you should see a comment on your pull request with a link to the preview of your docs.
In the example, we utilized a service user account. A service user is a user created in Azure Repos whose primary purpose is to generate a personal access token for use by a 3rd party service (like Redocly).
It's considered a good practice to create a service user.
When the build completes and is successful, Redocly posts a comment from the service user with the link to the preview.
If the build fails, Redocly posts a comment from the service user with a link the build logs where you can find more details for the cause of the failure (such as an invalid API definition).
Having problems? Let us know.