daml/ci/tell-slack-failed.yml

steps:
  - bash: |
      set -euo pipefail
      MESSAGE=$(git log --pretty=format:%s -n1)
      curl -XPOST \
           -i \
           -H 'Content-type: application/json' \
           --data "{\"text\":\"<!here> *FAILED* $(Agent.JobName): <https://dev.azure.com/digitalasset/daml/_build/results?buildId=$(Build.BuildId)|$MESSAGE>\n\"}" \
           $(Slack.team-daml)
    condition: and(failed(), eq(variables['Build.SourceBranchName'], 'master'))
extract slack fail message (#2009) 2019-07-04 17:22:22 +03:00			`steps:`
			`- bash: \|`
			`set -euo pipefail`
			`MESSAGE=$(git log --pretty=format:%s -n1)`
			`curl -XPOST \`
			`-i \`
			`-H 'Content-type: application/json' \`
record build times & statuses (#2016) 2019-07-05 14:35:30 +03:00			`--data "{\"text\":\"<!here> FAILED $(Agent.JobName): <https://dev.azure.com/digitalasset/daml/_build/results?buildId=$(Build.BuildId)\|$MESSAGE>\n\"}" \`
ci: alert Slack on PR build completion (#4286) One of the outputs of our brainstorming about how to make CI better was that it is annoying to have to "babysit" pull requests. This PR attempts to introduce a notification mechanism by which Azure will notify people on Slack when a build finishes, so they know they need to go and rerun or merge the corresponding PR. This commit also changes the existing $Slack.URL variable to $Slack.team-daml, to make more explicit where the Slack message is being sent to (Slack works with one token per destination channel). Both $Slack.URL and $Slack.team-daml are currently defined as the same token in Azure. CHANGELOG_BEGIN CHANGELOG_END 2020-02-03 18:29:13 +03:00			`$(Slack.team-daml)`
extract slack fail message (#2009) 2019-07-04 17:22:22 +03:00			`condition: and(failed(), eq(variables['Build.SourceBranchName'], 'master'))`