You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
Ubuntu
Reproduction steps
Add user to Jenkins with a matching Slack User ID configured in the user settings inside of Jenkins
Setup a Multibranch pipeline that builds based on changes to PRs
Using a slack send notification in the post stage of a Jenkins pipeline, like so:
post {
always {
slackSend (
channel: "#jenkinsbuilds",
notifyCommitters: "true",
color: 'good',
message: "Message from Jenkins Pipeline"
)
}
}
Expected Results
A slack notification should be sent to the user who made the commit.
Actual Results
On random occasions it will send a notification to a user who did not make any changes to the respective PR. Sometimes the user it sends the notification to has made no changes to the respective PR. This does not happen all the time, but rather sporadically without a clear pattern.
Anything else?
We have already double checked to ensure that the Jenkins users are configured properly with the correct Slack User IDs.
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Ubuntu
Reproduction steps
Expected Results
A slack notification should be sent to the user who made the commit.
Actual Results
On random occasions it will send a notification to a user who did not make any changes to the respective PR. Sometimes the user it sends the notification to has made no changes to the respective PR. This does not happen all the time, but rather sporadically without a clear pattern.
Anything else?
We have already double checked to ensure that the Jenkins users are configured properly with the correct Slack User IDs.
The text was updated successfully, but these errors were encountered: