Read about our upcoming Code of Conduct on this issue

notify.gitlab-ci.yml 1.35 KB
Newer Older
1
2
3
4
5
.notify-slack:
  image: alpine
  stage: notify
  dependencies: []
  cache: {}
6
7
  variables:
    MERGE_REQUEST_URL: ${CI_MERGE_REQUEST_PROJECT_URL}/-/merge_requests/${CI_MERGE_REQUEST_IID}
8
9
10
11
12
13
14
  before_script:
    - apk update && apk add git curl bash

notify-update-gitaly:
  extends:
    - .notify-slack
  rules:
15
    - if: '$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME == $GITALY_UPDATE_BRANCH'
16
17
18
19
20
21
22
23
      when: on_failure
      allow_failure: true
  variables:
    NOTIFY_CHANNEL: g_create_gitaly
    GITALY_UPDATE_BRANCH: release-tools/update-gitaly
  script:
    - echo "NOTIFY_CHANNEL is ${NOTIFY_CHANNEL}"
    - echo "CI_PIPELINE_URL is ${CI_PIPELINE_URL}"
24
25
26
27
28
29
30
31
32
33
34
35
36
    - scripts/slack ${NOTIFY_CHANNEL} "☠️ \`${GITALY_UPDATE_BRANCH}\` failed! ☠️ See ${CI_PIPELINE_URL} (triggered from ${MERGE_REQUEST_URL})" ci_failing "GitLab QA Bot"

notify-security-pipeline:
  extends:
    - .notify-slack
    - .delivery:rules:security-pipeline-merge-result-failure
  variables:
    NOTIFY_CHANNEL: f_upcoming_release
  script:
    - echo "NOTIFY_CHANNEL is ${NOTIFY_CHANNEL}"
    - echo "CI_PIPELINE_URL is ${CI_PIPELINE_URL}"
    # <!subteam^S0127FU8PDE> mentions the `@release-managers` group
    - scripts/slack ${NOTIFY_CHANNEL} "<!subteam^S0127FU8PDE> ☠️  Pipeline for merged result failed! ☠️ See ${CI_PIPELINE_URL} (triggered from ${MERGE_REQUEST_URL})" ci_failing "GitLab Release Tools Bot"