-
-
Notifications
You must be signed in to change notification settings - Fork 86
Open
Description
Hi,
We have updated the plugin to version 5.0.0 to use Microsoft Adaptive Cards. We have created a Workflow in Teams by using Webhook Template called Post to a channel when webhook required is a received:
Our previous configuration was as follows (here’s a simple example for when the build is a Success)::
post {
success {
withCredentials([string(credentialsId: "${env.MICROSOFT_TEAMS_CREDENTIAL}", variable: "WEBHOOK_URL")]) {
office365ConnectorSend webhookUrl: "${env.WEBHOOK_URL}",
message: "**Status**: Success \n **Build**: ${env.BUILD_NUMBER} \n **Commit**: ${env.GIT_COMMIT.take(7)} \n **More info**: [Jenkins](${env.BUILD_URL})",
color: '#58D68D'
}
}
With the new configuration (we’ve only added the adaptiveCards parameter)
post {
success {
withCredentials([string(credentialsId: "${env.MICROSOFT_TEAMS_CREDENTIAL}", variable: "WEBHOOK_URL")]) {
office365ConnectorSend webhookUrl: "${env.WEBHOOK_URL}",
message: "**Status**: Success \n **Build**: ${env.BUILD_NUMBER} \n **Commit**: ${env.GIT_COMMIT.take(7)} \n **More info**: [Jenkins](${env.BUILD_URL})",
color: '#58D68D',
adaptiveCards: true
}
}
We have several doubts/questions about the new notification format:
- Does it make sense to display "
Notification from node-app » main » master"? Isn't it redundant? - Does it make sense to show the build in the title? Previously, it didn't appear there; we displayed it in the message instead.
- Is the
color:parameter necessary? We've noticed that the color changes based on whether it's Success, Failure, etc.
Thanks in advance,
Regards
davidpatino, jgoncasu, moto999999, AndreaCesarEdnon, nicolasGutierrezGarcia1970 and 2 more
Metadata
Metadata
Assignees
Labels
No labels

