Slack

Today let’s have a look at how to integrate Slack to your CI pipeline. The CI platform we are using is DroneCI, which is a self-service Continuous Integration platform for busy development teams. 1. Benefits Well, there are many benefits to integrate Slack to your CI pipeline. Here are some of them: You can get notified when the CI pipeline is running, failed or succeeded. The notification will be sent to the Slack channel you specified. Therefore, you can easily track the CI pipeline status in the Slack channel. You can also get notified when someone pushes the code to the repository. This is very useful when you are working in a team. You can get notified when your team member pushes the code to the repository. Slack is a very popular communication tool. Your team is probably using it. Therefore, it’s very convenient to integrate Slack to your CI pipeline. 2. Prerequisites You have a Slack account. You have a DroneCI account. 3. Steps 3.1 Create Slack Channel Create channel for receiving the notification. Give a name, for example, #ci-pipeline. Remember the name, we will use it later. Specify the channel visibility. In this example, we will make it private. Then click Create. 3.2 Create Slack App Make sure you have the permission to create Slack App. If not, please contact your Slack administrator. ...

Recently I had a task to integrate Slack notification in Github Action workflow. Thanks to the repository slack-github-action, the work becomes much easier. The Slack integration works well when the payload only contains text and block. However, an error popped up while I changed the payload only with attachments. (We can add color to attachments which will highlight the message in Slack channel) The error was axios post failed, double check the payload being sent includes the keys Slack expects\n Error: no_text The first reaction after seeing the error is that I should add a text into the payload. But it turned out that the Slack message will only show the text content and ignore the attachment. ...