Hi team,
I have made a Jenkins job in the past for automating email reports. Last night, I applied a simple configuration change ("Configure" -> "Build Trigger" -> "Build periodically with parameters" -> remove one line at 4:12 AM UTC) while the scheduled job was running (4:11 AM UTC) that has nothing to do with the line I removed, and the scheduled job was triggered again after applying the configuration change at 4:17 AM UTC for some odd reason, hence sending two emails.
This seemed to be a bug on the Jenkins-side, so wanted to report this issue / give feedback.
Originally reported by jaypark9524, imported from: Jenkins job re-ran after configuration change
- assignee: ragesh_nair
- status: Open
- priority: Minor
- component(s): parameterized-trigger-plugin, rebuild-plugin
- label(s): jenkins
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 2025-12-07
Raw content of original issue
Hi team,
I have made a Jenkins job in the past for automating email reports. Last night, I applied a simple configuration change ("Configure" -> "Build Trigger" -> "Build periodically with parameters" -> remove one line at 4:12 AM UTC) while the scheduled job was running (4:11 AM UTC) that has nothing to do with the line I removed, and the scheduled job was triggered again after applying the configuration change at 4:17 AM UTC for some odd reason, hence sending two emails.
This seemed to be a bug on the Jenkins-side, so wanted to report this issue / give feedback.
- environment:
Jenkins 2.235.5, Chrome, MacOS
1 attachment
Hi team,
I have made a Jenkins job in the past for automating email reports. Last night, I applied a simple configuration change ("Configure" -> "Build Trigger" -> "Build periodically with parameters" -> remove one line at 4:12 AM UTC) while the scheduled job was running (4:11 AM UTC) that has nothing to do with the line I removed, and the scheduled job was triggered again after applying the configuration change at 4:17 AM UTC for some odd reason, hence sending two emails.
This seemed to be a bug on the Jenkins-side, so wanted to report this issue / give feedback.
Originally reported by jaypark9524, imported from: Jenkins job re-ran after configuration change
Raw content of original issue
Jenkins 2.235.5, Chrome, MacOS1 attachment