gearman plugin should not start if there are no jenkins master executors
Bug #1180515 reported by
Khai Do
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Jenkins Gearman Plugin |
Opinion
|
Undecided
|
Unassigned | ||
Bug Description
The gearman plugin requires a jenkins instance to have at least one executor on the master node to run management workers. Users can disable all jenkins master executors by setting the executors field to 0 in the jenkins global configuration. If that is the case then the Gearman plugin should probably not start and tell the user to enable at least one executor on the master.
Revision history for this message
| Khai Do (zaro0508) wrote | #1 |
| Changed in gearman-plugin: | |
| status: | New → Opinion |
To post a comment you must log in.
Looking at this issue again. I'm not quite that enforcing this requirement is the right behavior. I'm thinking of this specific case:
1. jenkins master and a few slaves all with executors on them.
2. user enables the gearman-plugin. gearman-plugin spawns a gearman worker for each executor.
3. user decides to disable the master by setting executors on master to 0.
Now do we automatically disable the gearman-pluign? disabling gearman-plugin would stop all executors. This doesn't seem right. I think it's better to allow gearman-plugin to run without this requirement, you just won't get the gearman management functionality (stop, set_description, etc..).