Ah, so you want to set up continuous integration (CI) testing for your Rust project, and you decided you wanted to use Azure Pipelines for it? Well, you're in the right place!
Azure Pipelines, like many other CI services, basically requires you to fully spell out all the steps to your CI. This is very handy if you have a complex CI pipeline, but is pretty inconvenient if you just want something that works. This project aims to bridge that gap. It also tries to guide you through how to even get Azure Pipelines set up in the first place, which can be a daunting thing to get right!
If you're curious what your CI will ultimately look like, go take a look
at tracing-timing's
CI
for example. By default, it tests on all platforms, checks that your
code compiles with and without any features it may have, and ensures
that your code works with an older Rust version. You can also
mix-and-match these checks if you wish.
To start, go take a look at the documentation.
You can find the documentation at https://crate-ci.github.io/azure-pipelines/. It includes a "getting started" guide, detailed setup instructions, documentation of CI configuration options, and information about how you can mix and match individual templates.
If you've done this before, and just want the standard YAML again for
azure-pipelines.yml, here it is:
stages:
- template: azure/stages.yml@templates
resources:
repositories:
- repository: templates
type: github
name: crate-ci/azure-pipelines
ref: refs/heads/v0.2
endpoint: YOU_NEED_TO_SET_THIS