Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 507311

Summary: Connectivity issues after SLES upgrade
Product: Community Reporter: Jens Reimann <jreimann>
Component: CI-JenkinsAssignee: CI Admin Inbox <ci.admin-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: blocker    
Priority: P3 CC: frederic.gurr, webmaster
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Jens Reimann CLA 2016-11-09 11:43:49 EST 
On the Eclipse NeoSCADA HIPP instance [1] we do have some issues, it looks to me like the SLES upgrade did change something related to the proxy setup.

e.g. Job [2] is unable to fetch artifacts anymore from the package drone instance at [3], this was working before.

I do remember that there were some issues with the proxies in the past, packagedrone.eclipse.org is running on the new google cloud infrastructure.

However issuing a standard WGET to access [3], results in a proxy request and works fine. But P2 seems to have an issue.

[1] https://hudson.eclipse.org/eclipsescada
[2] https://hudson.eclipse.org/eclipsescada/job/org.eclipse.scada.ide-master/288/console
[3] http://packagedrone.eclipse.org
Comment 1 Frederic Gurr CLA 2016-11-11 16:40:13 EST 
Removing "<nonProxyHosts>" tag from the Maven settings.xml fixed the issue. Not sure why this became an issue after the SLES upgrade, but I will try to chase it up.