Add Azure Pipelines configuration

[pietroalbini]

Huge thanks to ＠johnterickson and ＠willsmythe for writing the initial config! ❤️
I applied some changes to the initial config and disabled most of the builders since we're not going to run all of them during the initial step for the evaluation.

More details about our plans for the Azure Pipelines evaluation.

r? ＠alexcrichton ＠kennytm
cc ＠rust-lang/infra ＠ethomson ＠rylev

[pietroalbini]

Azure Pipelines is not yet configured on the repository btw.

[johnterickson]

Looking good!

I do need to give credit to @willsmythe - he took some of my initial work and brought it a lot closer to being production ready.

One thing I noticed in my runs is that sometimes I would see OOM failures in some of the dist-* configs. These seems to work on retry. I know we're already chatting about some bigger VMs and I think that should help.

Both Azure Storage and S3 should work well, but just wanted to point out two things:

1. You'll probably want to use separate containers/buckets just in case cached layers/sccache from one affects the other.
2. If you see a network I/O perf regression here, then you might want to consider using Azure Storage accounts created in the same region as your builds are running in. This will put them in the same datacenter.

[zachChilders]

Consider putting any bash script longer than a few lines in a standalone script that can be invoked instead of inlined into yml, perhaps under a /scripts folder.

This allows you to easily run & lint the script, whereas it takes extra steps to do so in yaml.

[pietroalbini]

One thing I noticed in my runs is that sometimes I would see OOM failures in some of the dist-* configs. These seems to work on retry. I know we're already chatting about some bigger VMs and I think that should help.

That's good to know. Let's see how our first builds will go.

You'll probably want to use separate containers/buckets just in case cached layers/sccache from one affects the other.

Yep, that was the plan. I think there shouldn't be any issue merging the buckets (for example the Docker cache contains host machine data in the hash), but let's not risk it.

If you see a network I/O perf regression here, then you might want to consider using Azure Storage accounts created in the same region as your builds are running in. This will put them in the same datacenter.

At least for now let's keep things in AWS (mostly because it's one less cloud platform and sets of perms to manage), but we'll surely look into the Azure storage offering if the perf is too bad.

---

I'll try to address the other comments tomorrow, if I have some free time after the release is done.

[shepmaster]

just in case cached layers/sccache from one affects the other.

One thing that CircleCI does that I appreciate is the ability to have "tiered" caches. For a Ruby app I help with, it looks like:

      - restore_cache:
          keys:
            - ruby-dependency-cache--v4--{{ arch }}-{{ .Branch }}-{{ checksum "Gemfile.lock" }}
            - ruby-dependency-cache--v4--{{ arch }}-{{ .Branch }}-
            - ruby-dependency-cache--v4--{{ arch }}-

When restoring a cache, it uses the first matching key. This means that new branches start from a cache from the master branch, but will create a differently-named cache to avoid unintentional cache busting.

[alexcrichton]

Sorry I'm pretty slammed at the moment with a lot of things, but looking over this the non-azure configuration bits all look reasonable to me, and I'm happy to review the azure configuration bits on my own time when I get a chance. (I also trust y'all!)

Feel free to r=me when you're comfortable landing yourself.

[pietroalbini]

@bors try

Note: this won't start Azure Pipelines yet.

[bors]

⌛ Trying commit 4965ffd with merge 8ffb1f01b864abe7a25e0a86034407a103e08dd7...

[bors]

⌛ Testing commit 2244ca3 with merge 8798cbc1646c5505b2f457b942929576d3f9c180...

[Centril]

@bors retry

[rust-highfive]

Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.

Cloning into 'rust-lang/rust'...
travis_time:end:0ae73e5a:start=1558719219386312087,finish=1558719225043283417,duration=5656971330
$ cd rust-lang/rust
$ git checkout -qf 8798cbc1646c5505b2f457b942929576d3f9c180
fatal: reference is not a tree: 8798cbc1646c5505b2f457b942929576d3f9c180
The command "git checkout -qf 8798cbc1646c5505b2f457b942929576d3f9c180" failed and exited with 128 during .
Your build has been stopped.

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @TimNN. (Feature Requests)

[bors]

⌛ Testing commit 2244ca3 with merge 0ae26befeb61b6dccc8a14c5e6ddaa661e46b3e9...

[pietroalbini]

@bors retry

Yielding priority to the rollup.

[rust-highfive]

Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.

Cloning into 'rust-lang/rust'...
travis_time:end:0c225c27:start=1558720300440056536,finish=1558720306140163143,duration=5700106607
$ cd rust-lang/rust
$ git checkout -qf 0ae26befeb61b6dccc8a14c5e6ddaa661e46b3e9
fatal: reference is not a tree: 0ae26befeb61b6dccc8a14c5e6ddaa661e46b3e9
The command "git checkout -qf 0ae26befeb61b6dccc8a14c5e6ddaa661e46b3e9" failed and exited with 128 during .
Your build has been stopped.

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @TimNN. (Feature Requests)

[bors]

⌛ Testing commit 2244ca3 with merge dec4c52...

[bors]

☀️ Test successful - checks-travis, status-appveyor
Approved by: alexcrichton
Pushing dec4c52 to master...

[pietroalbini]

Huge thanks to everyone involved in getting this PR landed! ❤️

Now that the core configuration is merged in the repo there are some (small and big) papercuts to fix, and I opened an issue for each of them with the azure-evaluation label. If you want to help us fixing them please claim am issue (typing @rustbot claim in a comment) and send a PR!