When setting things up via the UI, we can use the Test Connection button to ensure that Jenkins can reach Slack.
We can also specify additional fields if desired, such as commit information used for the Jenkins job, custom messages, custom bot icons, and more: The Slack channel name or member ID to send messages to.The name of the credentials to use – the ones we added previously.Which build phases to send messages for (start, success, failure, etc).However, there are a few required pieces of information:
Generally, most of the default values are sufficient. Once selected, there are lots of available inputs to the Slack Notification action. When we drop down the Add post-build action menu, we'll find Slack Notifications: In order to integrate a traditional job with Slack, we'll use a post-build action. These are configured via the Jenkins user interface. Traditional Jenkins jobs usually execute one or more actions to accomplish their goals.
0 kommentar(er)
