![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Components:
|
swarm |
|
Created:
|
20/Nov/13 10:37 AM
|
|
Description:
|
Whenever there is a problem with a swarm slave that causes its disconnection the slave just disappears. This prevents on first acknowledging there is a problem with that particular slave and secondly finding out more from logs.
One possible solution is to have a "sticky" option in slave configuration so to make it persistent in case it goes offline.
Another possible solution would be to add in general configuration some time based options for "swarm" specific slaves:
- connection timeout (ex 15 min)
- removal timeout (ex: 1 day)
The basic idea is the same, to provide more transparency of the status of slaves instead of hiding them when something goes wrong.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jose Sa
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
