Bugzilla – Full Text Bug Listing
| Summary: | Make hudson https urls work reliable | ||
|---|---|---|---|
| Product: | [Technology] Hudson | Reporter: | Dennis Huebner <dennis.huebner> |
| Component: | Core | Assignee: | Winston Prakash <winston.prakash> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | adolfosbh, mygwaymark, pwebster, sbouchet, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Dennis Huebner
I suspect this is really an issue with Hudson itself. Assigning to the Hudson team for comment. -M. (In reply to comment #1) > I suspect this is really an issue with Hudson itself. Assigning to the Hudson > team for comment. > > -M. Now I'm some times getting 502 Bad Gateway accessing https URL's : INFO: importtargetdefinition '-DuseMirror=false' '-A' '/opt/users/hudsonbuild/.hudson/jobs/Xtext-test/workspace//org.eclipse.xtext.git/releng/org.eclipse.xtext.releng/releng/tests/tests-galileo.target' INFO: System property http.proxyHost has been set to proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="*.eclipse.org" -Dhttps.nonProxyHosts="*.eclipse.org" by an external source. This value will be overwritten using the values from the preferences WARN: Server returned lastModified <= 0 for https://hudson.eclipse.org/hudson/job/Xpand-nightly-HEAD/lastSuccessfulBuild/artifact/xpand.p2.repository/artifacts.jar WARN: Server returned lastModified <= 0 for https://hudson.eclipse.org/hudson/job/Xtext-nightly-Maintenance/lastSuccessfulBuild/artifact/xtext.p2.repository/artifacts.jar WARN: Server returned lastModified <= 0 for https://hudson.eclipse.org/hudson/job/MWE-Language-nightly-HEAD/lastSuccessfulBuild/artifact/mwe2lang.p2.repository/artifacts.jar Unable to load all units for Software Site container of target /opt/users/hudsonbuild/.hudson/jobs/Xtext-test/workspace//org.eclipse.xtext.git/releng/org.eclipse.xtext.releng/releng/tests/tests-galileo.target [0]An error occurred while collecting items to be installed [0.2]session context was:(profile=TARGET_DEFINITION:local:1323688989233.target, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). [0.2]HTTP Server 'Bad Gateway' : https://hudson.eclipse.org/hudson/job/Xpand-nightly-HEAD/lastSuccessfulBuild/artifact/xpand.p2.repository/binary/org.eclipse.xpand_root_1.2.1.v201112070721 Caused by: [0.2][0.2]HttpClient connection error response code 502. Terminating xvnc. Denis, I will look at this issue and other issues you assigned to me, once I get some breathing time from the Hudson Eclipse move. However, if you want me to look in to any of the bugs urgently, let me know. I will take some time off from the eclipse move work to look in to those urgent bugs. just my 2 cents, but i think p2 cannot access to any https repository at all without credential. (In reply to comment #4) > just my 2 cents, but i think p2 cannot access to any https repository at all > without credential. Hmmm... How can it sometimes work and sometimes not? (In reply to comment #5) > (In reply to comment #4) > > just my 2 cents, but i think p2 cannot access to any https repository at all > > without credential. > > Hmmm... How can it sometimes work and sometimes not? i was just looking at the first lines saying : (In reply to comment #0) > As suggested by web masters I changed URL's from: > -Dxpand.p2.repository=file:/opt/users/hudsonbuild/.hudson/jobs/Xpand-nightly-HEAD/lastSuccessful/archive/xpand.p2.repository/ > -Dxtext.p2.repository=file:/opt/users/hudsonbuild/.hudson/jobs/Xtext-nightly-HEAD/lastSuccessful/archive/xtext.p2.repository/ > > to: > -Dxpand.p2.repository=https://hudson.eclipse.org/hudson/job/Xpand-nightly-HEAD/lastSuccessfulBuild/artifact/xpand.p2.repository/ > -Dxtext.p2.repository=https://hudson.eclipse.org/hudson/job/Xtext-nightly-HEAD/lastSuccessfulBuild/artifact/xtext.p2.repository/ > And this is just not working with p2. p2 can read repo from http, or file, but not from https. (In reply to comment #6) > And this is just not working with p2. p2 can read repo from http, or file, but > not from https. I can tweak the rewriterules so that http://hudson.eclipse.org/hudson/job/*/workspace and http://hudson.eclipse.org/hudson/job/*/lastSuccessfulBuild/artifact/ are allowed over plain http. Would that help? (In reply to comment #7) > (In reply to comment #6) > > And this is just not working with p2. p2 can read repo from http, or file, but > > not from https. > > I can tweak the rewriterules so that > http://hudson.eclipse.org/hudson/job/*/workspace and > http://hudson.eclipse.org/hudson/job/*/lastSuccessfulBuild/artifact/ are > allowed over plain http. Would that help? Let's give it a try! @Stephane: https works too. Just try to use some https update site. Why do you think it wouldn't work? (In reply to comment #8) > > http://hudson.eclipse.org/hudson/job/*/workspace and > > http://hudson.eclipse.org/hudson/job/*/lastSuccessfulBuild/artifact/ are > > allowed over plain http. Would that help? > > Let's give it a try! Actually, I've changed the server config to allow all Hudson requests from our internal network to flow on plain http. Outside access requires https. Give that a try. (In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > And this is just not working with p2. p2 can read repo from http, or file, but > > > not from https. > > > > I can tweak the rewriterules so that > > http://hudson.eclipse.org/hudson/job/*/workspace and > > http://hudson.eclipse.org/hudson/job/*/lastSuccessfulBuild/artifact/ are > > allowed over plain http. Would that help? > > Let's give it a try! > > @Stephane: https works too. Just try to use some https update site. Why do you > think it wouldn't work? because I tried to use some https:// p2 repo in Eclipse and b3 and did not worked because of required credential. now, as denis said, we can access to any https p2 repo on hudson without problem, so you can ignore my comments :) (In reply to comment #9) > (In reply to comment #8) > > > http://hudson.eclipse.org/hudson/job/*/workspace and > > > http://hudson.eclipse.org/hudson/job/*/lastSuccessfulBuild/artifact/ are > > > allowed over plain http. Would that help? > > > > Let's give it a try! > > Actually, I've changed the server config to allow all Hudson requests from our > internal network to flow on plain http. Outside access requires https. > > Give that a try. Doesn't work reliable ether :( It looks like a hudson issue... INFO: System property http.proxyHost has been set to proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="*.eclipse.org" -Dhttps.nonProxyHosts="*.eclipse.org" by an external source. This value will be overwritten using the values from the preferences Unable to load all units for Software Site container of target <https://hudson.eclipse.org/hudson/job/Xtext-test/ws//org.eclipse.xtext.git/releng/org.eclipse.xtext.releng/releng/tests/tests-galileo.target> [0]Problems loading repositories [0.2]Unable to read repository at http://hudson.eclipse.org/hudson/job/Xtext-nightly-HEAD/lastSuccessfulBuild/artifact/xtext.p2.repository/. Caused by: [0.2]java.io.IOException: http://hudson.eclipse.org/hudson/job/Xtext-nightly-HEAD/lastSuccessfulBuild/artifact/xtext.p2.repository/ is not a valid repository location. Terminating xvnc. [FINDBUGS] Skipping publisher since build result is FAILURE Is this still an issue? If so can somebody give me details on how to reproduce this, so that I can take a look at it. Two thins to consider - Eclipse Hudson is now on Jetty - In Hudson 3.0.0 we moved from Winstone server to Jetty. So my question is, do we still see this with Jetty as the container? (In reply to comment #12) > Is this still an issue? If so can somebody give me details on how to > reproduce this, so that I can take a look at it. > > Two thins to consider > > - Eclipse Hudson is now on Jetty > - In Hudson 3.0.0 we moved from Winstone server to Jetty. > > So my question is, do we still see this with Jetty as the container? It's works better now. We get 503 responses or broken pipe errors sometimes, but I think in those cases that was not a hudson issue. Dennis, thanks. Marking this as "RESOLVED WORSFORME" |