Bugzilla – Full Text Bug Listing
| Summary: | Builds on Hudson Slave 2 Failing | ||
|---|---|---|---|
| Product: | Community | Reporter: | Terran Gilman <trip> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | thomas |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Terran Gilman
It appears that slave 1 has now stalled out again. And the VTP build is hung. What's the binding string to force it to run on the master. I tried "Master" but it failed to match anything. I just built the project on the master and received the same error. I have confirmed that the URL used is correct. Is there some sort of special configuration i need in my builds now? This build was working perfectly for weeks before it started to fail thursday night. The issue seems to be related to the ' ' enclosing the proxy information in the java command. If I leave the quotes in, I can force this error on any hudson node(command line), if I remove then it works. I'll keep digging, but I'm unaware of any changes to the hudson setup. -M. Looking back at the command line for the last couple successful builds, I can't see any changes. The single quotes were there for the successes. Let me know what I can do to help. Thomas, it looks like you made some changes to the buckminster install last thursday. Is it possible something was updated and is the source of this issue? -M. It might. I think the old version was lacking the needed org.eclipse.core.net fragment for the x86_64 version which meant that it didn't pick up the proxy environment correctly. The current version does. I'm not sure but I think that might actually conflict with the settings passed on the command line. Trip, can you try without all -D settings that are related to proxies and just rely on whatever is passed (implicitly) in the environment and see what happens? I'm not explicitly declaring any proxy settings in my build configuration. The quoted settings appear to be coming directly from Hudson. I am unable to make these changes myself. The settings are being added to the command line automatically. Can someone please try to implement Thomas's fix on the hudson server? I've removed the proxy details from the Buckminster tools setup in hudson(this affects all nodes), and your build seems to be happier. However I'm not sure what impact this will have on other jobs. -M. It looks like everything is working perfectly. I don't think the changes made should affect any other buckminster builds. My build returned to "normal" with the changes without need for build configuration changes. I would assume the other builds would behave the same. If you want to make other changes to the buckminster system on hudson. I'll offer up our project as a test bed for it. It is pretty straightforward as build configurations go and should be a nice acid test for you. Just let me know and i'll make sure someone from our team can work with you. |