Issue Type: Bug Bug
Assignee: ramapulavarthi
Components: port-allocator
Created: 24/Jul/13 2:59 PM
Description:

We upgraded Port allocator (and lots of other things), and found the strange and unexpected behaviour that our builds seemed not to be running correctly on slaves.

After much digging, the finger points to the upgrade of port allocator.

The following groovy script shows why:

def q = Jenkins.getInstance().getQueue();
q.getClass().getDeclaredFields().each() { it->println "$it.name"; }

def fld = ResourceController.class.getDeclaredField("inUse");
fld.setAccessible(true);
def result = fld.get(q);

def fld2 = ResourceList.class.getDeclaredField("all");
fld2.setAccessible(true);

result.each() {

def result2 = fld2.get(it);

result2.each() { res -> println "... ${res.class}"; }

}

Gives

...
... class hudson.model.Resource
... class hudson.model.Resource
Result: {standalone port SHUTDOWN_PORT(1)=W1, standalone port HTTP_PORT(1)=W1}

The first build through is blocking every other build, which just sits there for multiple hours until complete. Since they are on entirely different slaves (computers), this is particularly wrong.

We had to downgrade to 1.5 to fix this.

Project: Jenkins
Priority: Major Major
Reporter: magnayn
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to