From ef211c96c01fbe87abfb4f285372d2b19594e30c Mon Sep 17 00:00:00 2001
From: Jonathan Lebon <jonathan@jlebon.com>
Date: Wed, 16 Nov 2022 12:34:59 -0500
Subject: [PATCH] jenkins/config: add empty `room` field

After 27693a6, the Slack plugin fails to send messages on new Jenkins instances with:

    java.lang.IllegalArgumentException: Project Channel or Slack User ID
    must be specified.

This seems to be due to some bug in the plugin where without a `room`
setting, it doesn't know to rely on the default room associated with the
token. This is filed upstream in:

https://github.com/jenkinsci/slack-plugin/issues/857

Short-term, let's just work around this by specifying an empty `room`.
---
 jenkins/config/slack.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/jenkins/config/slack.yaml b/jenkins/config/slack.yaml
index 181d9ea3f..e7e0e41a8 100644
--- a/jenkins/config/slack.yaml
+++ b/jenkins/config/slack.yaml
@@ -2,3 +2,5 @@ unclassified:
   slackNotifier:
     teamDomain: coreos
     tokenCredentialId: slack-api-token
+    # https://github.com/jenkinsci/slack-plugin/issues/857
+    room: ""