[JIRA] (JENKINS-59086) PCT failing in BOM due to UC outage despite using -war

0 views
Skip to first unread message

jglick@cloudbees.com (JIRA)

unread,
Aug 26, 2019, 9:49:02 AM8/26/19
to jenkinsc...@googlegroups.com
Jesse Glick created an issue
 
Jenkins / Bug JENKINS-59086
PCT failing in BOM due to UC outage despite using -war
Issue Type: Bug Bug
Assignee: Jesse Glick
Components: bom, plugin-compat-tester
Created: 2019-08-26 13:48
Priority: Critical Critical
Reporter: Jesse Glick
 Hook: org.jenkins.tools.test.hook.MultiParentCompileHook
 Loaded multi-parent compile hook
 Scanned contents of /home/jenkins/workspace/g.jenkins-ci.plugins-plugin-3.49/megawar.war: {"id":"default","core":{"name":"core","version":"2.176.2","url":"https://foobar"},"plugins":{...}}
 Exception in thread "main" java.lang.RuntimeException: Invalid update center url : http://updates.jenkins-ci.org/update-center.json
 	at org.jenkins.tools.test.PluginCompatTester.extractUpdateCenterData(PluginCompatTester.java:583)
 	at org.jenkins.tools.test.PluginCompatTester.testPlugins(PluginCompatTester.java:183)
 	at org.jenkins.tools.test.PluginCompatTesterCli.main(PluginCompatTesterCli.java:164)
 Caused by: java.net.ConnectException: Connection timed out (Connection timed out)
 	at java.net.PlainSocketImpl.socketConnect(Native Method)
 	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
 	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
 	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 	at java.net.Socket.connect(Socket.java:589)
 	at java.net.Socket.connect(Socket.java:538)
 	at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
 	at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
 	at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
 	at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
 	at sun.net.www.http.HttpClient.New(HttpClient.java:339)
 	at sun.net.www.http.HttpClient.New(HttpClient.java:357)
 	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1226)
 	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
 	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
 	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:990)
 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570)
 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
 	at java.net.URL.openStream(URL.java:1057)
 	at org.jenkins.tools.test.PluginCompatTester.extractUpdateCenterData(PluginCompatTester.java:581)

suggests a transient network outage. But why would PCT be paying any attention to the UC to begin with? -war was passed and the build should not depend on the UC in any way.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages