'Jenkins launches 2 builds when manually triggered
I've noticed a recent issue in both our instances of Jenkins. When launching a job manually, it launches twice. I've no idea what is causing it, but it's happening across multiple jobs. I used to think it was a display issue because cancelling one of the jobs would cancel the other. But, once I check the rule for not building concurrently, I see the second job queued up and have it fire afterwards and if the job is something like update a local folder from git, the second build will fail (since the first one already updated) which shows me that they are not the same build but instead are two different ones firing up at the same time. For all intent and purposes, it's a trivial issue, but not knowing what's causing it is driving me insane.
Anyone ran into anything like this before?
Solution 1:[1]
Update: At one point, updating to a newer version of Jenkins fixed this issue. I am still not sure what exactly was happening, but for future reference, the issue was that any build with parameters would double trigger.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Niehm |