rust/.azure-pipelines/master.yml

#
# Azure Pipelines job to publish toolstate. Only triggers on pushes to master.
#

pr: none
trigger:
  - master

variables:
- group: prod-credentials

pool:
  vmImage: ubuntu-16.04

steps:
- checkout: self
  fetchDepth: 2

- script: |
    export MESSAGE_FILE=$(mktemp -t msg.XXXXXX)
    . src/ci/docker/x86_64-gnu-tools/repo.sh
    commit_toolstate_change "$MESSAGE_FILE" "$BUILD_SOURCESDIRECTORY/src/tools/publish_toolstate.py" "$(git rev-parse HEAD)" "$(git log --format=%s -n1 HEAD)" "$MESSAGE_FILE" "$TOOLSTATE_REPO_ACCESS_TOKEN"
  displayName: Publish toolstate
  env:
    TOOLSTATE_REPO_ACCESS_TOKEN: $(TOOLSTATE_REPO_ACCESS_TOKEN)
Add Azure Pipelines 2019-05-06 13:15:52 -05:00			`#`
			`# Azure Pipelines job to publish toolstate. Only triggers on pushes to master.`
			`#`

			`pr: none`
			`trigger:`
ci: disable builders not useful during the evaluation 2019-05-13 03:13:23 -05:00			`- master`
Add Azure Pipelines 2019-05-06 13:15:52 -05:00
ci: Enable toolstate tracking on Azure Currently just run it through its paces but don't actually push to official locations. Instead let's just push to a separate fork (mine) as well as open issues in a separate fork (mine). Make sure that people aren't pinged for these issues as well! This should hopefully ensure that everything is working on Azure and give us a chance to work through any issues that come up. 2019-06-12 09:59:20 -05:00			`variables:`
			`- group: prod-credentials`

Add Azure Pipelines 2019-05-06 13:15:52 -05:00			`pool:`
			`vmImage: ubuntu-16.04`

ci: remove trailing whitespaces from azure config 2019-05-13 02:55:12 -05:00			`steps:`
Add Azure Pipelines 2019-05-06 13:15:52 -05:00			`- checkout: self`
			`fetchDepth: 2`

			`- script: \|`
			`export MESSAGE_FILE=$(mktemp -t msg.XXXXXX)`
			`. src/ci/docker/x86_64-gnu-tools/repo.sh`
ci: Enable toolstate tracking on Azure Currently just run it through its paces but don't actually push to official locations. Instead let's just push to a separate fork (mine) as well as open issues in a separate fork (mine). Make sure that people aren't pinged for these issues as well! This should hopefully ensure that everything is working on Azure and give us a chance to work through any issues that come up. 2019-06-12 09:59:20 -05:00			`commit_toolstate_change "$MESSAGE_FILE" "$BUILD_SOURCESDIRECTORY/src/tools/publish_toolstate.py" "$(git rev-parse HEAD)" "$(git log --format=%s -n1 HEAD)" "$MESSAGE_FILE" "$TOOLSTATE_REPO_ACCESS_TOKEN"`
ci: remove trailing whitespaces from azure config 2019-05-13 02:55:12 -05:00			`displayName: Publish toolstate`
Add Azure Pipelines 2019-05-06 13:15:52 -05:00			`env:`
ci: Enable toolstate tracking on Azure Currently just run it through its paces but don't actually push to official locations. Instead let's just push to a separate fork (mine) as well as open issues in a separate fork (mine). Make sure that people aren't pinged for these issues as well! This should hopefully ensure that everything is working on Azure and give us a chance to work through any issues that come up. 2019-06-12 09:59:20 -05:00			`TOOLSTATE_REPO_ACCESS_TOKEN: $(TOOLSTATE_REPO_ACCESS_TOKEN)`