![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
mansion-cloud |
|
Created:
|
11/Jul/14 4:55 PM
|
|
Description:
|
In Jenkins versions > 1.532, MansionComputers are terminated immediately after coming online, before they can be assigned buildable items from the queue.
This happens if the computer takes longer to connect than MansionRetentionStrategy#TIMEOUT
The root cause is hudson.model.Executor#getIdleStartMilliseconds() uses Computer#getConnectTime() to determine idleness if no jobs have been run. However, Computer#connectTime is set when the computer starts connecting.
The solution is to track onlineTime for a MansionComputer and to use that when calculating idleness.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
recampbell
|
|
|
|
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/d/optout.
