Skip to content

Removes Slack notifications for #qa-master

James Nutt requested to merge sg/remove-notify-slack into master

What does this MR do and why?

This MR removes slack notifications from this project's pipeline.

The master pipeline definitions have moved to the GitLab project, but sometimes this project's pipeline still notifies the master triage channel.

Background

This project pushed a slack notification for a failed test run based on an incorrectly packaged omnibus build.

build-component_shas 00:00

SHAs of GitLab Components

gitlab-rails : fdcd1104281f9da6cf8b9a8bf295d04a1ce69d0f
gitlab-shell : 977a7e80f03db2d2e2646abfc6ad9d95bfc71fb9
gitlab-pages : f62ebec61d2bbdd1810b30ebc906737cc0dc4481
gitaly : 568197eab305e160229690d89cf7a6fdce2dfa3c
gitlab-elasticsearch-indexer : 4dfd8f10c41f4a9b65b9a8197e881776c4695b90
gitlab-kas : 88774e3471a8ef46962e1be775b815bceca37734

The commit for gitlab-rails commit references 3.1.2 of gitlab-elasticsearch-indexer but the commit for gitlab-elasticsearch-indexer references 3.2.0

https://gitlab.com/gitlab-org/gitlab/-/issues/386653

It was mentioned that the pipeline definitions for this project's master pipeline are outdated and unreliable.

This MR avoids to reduce confusion during triage by removing the slack notifications.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by James Nutt

Merge request reports