-
New Feature
-
Resolution: Fixed
-
Minor
-
None
-
-
3.30
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.
- links to
[JENKINS-20668] Persist Swarm agents when they go offline
Jose Sa
created issue -
| Workflow | Original: JNJira [ 152477 ] | New: JNJira + In-Review [ 178214 ] |
| Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] |
Basil Crow
made changes -
| Issue Type | Original: Improvement [ 4 ] | New: New Feature [ 2 ] |
Basil Crow
made changes -
| Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Basil Crow
made changes -
| Summary | Original: Persist Jenkins swarm slaves when they go offline | New: Persist Swarm agents when they go offline |
Basil Crow
made changes -
| Released As | New: 3.30 | |
| Assignee | New: Richard [ rimitchell ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Basil Crow
made changes -
| Remote Link | New: This issue links to "jenkinsci/swarm-plugin#368 (Web Link)" [ 27373 ] |
