I’m experiencing an issue with Jenkins where it keeps posting excessive comments on our JIRA issues. This problem is particularly noticeable when we use matrix builds because each build generates a comment.
Our JIRA comments are becoming overwhelmed with automated notifications from Jenkins. There are only a few genuine user comments, but they are drowned out by around 15-20 repetitive comments generated by Jenkins on every build change.
It’s challenging to sift through this clutter and locate actual user feedback. Does anyone have a solution to minimize these automated messages or know of a setting that could help streamline this process?
i had this issue too! just go to the jenkins jira plugin settings and look for the ‘comment on issues’ option. uncheck it for matrix builds. also, u can set it to only post comments on failures, it really makes a difference!
Here’s what worked for me: I changed the JIRA plugin to use a different notification strategy. Instead of commenting on every build, I set up a custom field in JIRA that updates with the latest build status. You still get build info without all the comment spam. Look for this in the Advanced section of the JIRA plugin config. You could also create a separate JIRA project just for build notifications and point Jenkins there instead of your main project. The trick is keeping build notifications separate from your actual dev discussions.
We had the same problem and fixed it with conditional commenting in our Jenkins pipeline. Just modify your pipeline script to only comment on JIRA when specific conditions are met, not every single build. I set mine to comment only when the build result changes from the previous one, or just on failures and successful prod deployments. You can also batch multiple build results into one comment instead of spamming new ones each time. This cut our comment noise by 80% but we still catch all the important build status changes. Takes some groovy scripting to set up, but it’s totally worth it for cleaner issue tracking.