Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369750 - Proxy settings defined incorrectly for buckminster
Summary: Proxy settings defined incorrectly for buckminster
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-25 16:41 EST by Michal Ruzicka CLA
Modified: 2012-02-06 06:36 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Ruzicka CLA 2012-01-25 16:41:15 EST
In the emf builds we see buckminster being invoked (in the frame of a buckminster build step) like this:

/shared/common/sun-jdk1.6.0_21_i586/bin/java -Dbuckminster.output.root=/opt/users/hudsonbuild/workspace/emf-core-head/buckminster.output -Dbuckminster.temp.root=/opt/users/hudsonbuild/workspace/emf-core-head/buckminster.temp '-Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="*.eclipse.org" -Dhttps.nonProxyHosts="*.eclipse.org"' -Dcheckout.location=/opt/users/hudsonbuild/workspace/emf-core-head/emf/releng/ -Dgit.clones.root=/opt/users/hudsonbuild/workspace/emf-core-head/buildroot/git -Demf.clone.root=/opt/users/hudsonbuild/workspace/emf-core-head/emf -jar /shared/common/buckminster-3.7/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar -application org.eclipse.buckminster.cmdline.headless -data /opt/users/hudsonbuild/workspace/emf-core-head/buildroot/buckminster.workspace --loglevel info -S /opt/users/hudsonbuild/workspace/emf-core-head/commands.txt

please note the single quotes around:

'-Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="*.eclipse.org" -Dhttps.nonProxyHosts="*.eclipse.org"'

which is interpreted as a single argument, effectively defining a single property - http.proxyHost - to have the value of the rest of the argument string:
proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="*.eclipse.org"

which is obviously not correct and forces us to redefine the proxy setting properties in the build job configurations

the buckminster installation known to suffer from this problem is: Buckminster 3.7
(but others my be affected too)

Could you please update the buckminster installation definition(s) so that the proxy settings are defined correctly?
Comment 1 Eclipse Webmaster CLA 2012-01-27 21:47:16 EST
These options are passed in via hudson.  I've updated the listing in hudson to put each item on a separate line.  Does that help?

-M.
Comment 2 Michal Ruzicka CLA 2012-02-02 15:18:08 EST
It does help, thank you.
The single quotes are gone and so all the individual proxy settings properties are being set now.
But unfortunately, the properties defining non-proxy hosts (http.nonProxyHosts, https.nonProxyHosts) are set to:
  "*.eclipse.org"
verbatim (i.e. including the double quotes).

Could you please remove the the double quotes from the  definitions, yet?
Comment 3 Eclipse Webmaster CLA 2012-02-03 11:03:43 EST
Ok, done.

-M.
Comment 4 Michal Ruzicka CLA 2012-02-06 06:36:35 EST
It works now, thank you.