521edee2e5
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.
26 lines
639 B
YAML
26 lines
639 B
YAML
#
|
|
# 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)
|