Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Won't Fix
-
Component/s: filesystem_scm-plugin
-
Labels:None
-
Similar Issues:
Description
if polling is enabled hudson will automatically trigger jobs if the workspace is still empty. But this should only happen if a node is available to execute the job. Otherwise jobs will get triggered as soon nodes disconnect.
Proposal is to add an option to disable this behavior and/or consider making it default behavior to not trigger jobs on disconnect.
Attachments
Activity
mbien
created issue -
It should be Hudson's bug, not an SCM. And I tested on 1.336, can't reproduce the problem.
samngms
added a comment - It should be Hudson's bug, not an SCM. And I tested on 1.336, can't reproduce the problem. samngms
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Resolution | Won't Fix [ 2 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
can't we reopen it and move it to the correct component? I haven't found a general hudson component.
mbien
added a comment - can't we reopen it and move it to the correct component? I haven't found a general hudson component. | Workflow | JNJira [ 137404 ] | JNJira + In-Review [ 187491 ] |
I tested on 1.336, a disconnected node doesn't trigger a polling.
But anyway, I think it is a good idea to add a checking before entering the polling event.
As for whether it should be the default behavior, it is under Hudson's control, not a plugin's control.