This chapter shows how to integrate with FeaturePeek when using the Azure Pipelines continuous integration service.
Example CI config
If you already have your config file set up, simply append the FeaturePeek CI command after your build phase.
If you don't have your config file set up yet, take a look at these examples provided by Microsoft to get started.
/azure-pipelines.yml file should look something like this:
# /azure-pipelines.yml # Starter pipeline # Start with a minimal pipeline that you can customize to build and deploy your code. # Add steps that build, run tests, deploy, and more: # https://aka.ms/yaml trigger: branches: include: - '*' pool: vmImage: 'ubuntu-latest' steps: - script: yarn build displayName: 'Build front-end assets' - script: bash <(curl -s https://peek.run/ci) displayName: 'Ping FeaturePeek'
Note: The command in the snippet above is just for static builds — if you are building a Docker image, you'll need to pass in more arguments.
Try it out
Try opening a new pull request that contain the changes in this chapter. When your CI finishes successfully, you should see the FeaturePeek bot comment a link on your pull request. If not, consult our Troubleshooting section.