[JIRA] (JENKINS-36256) "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically
Title: Message Title Daniel Possamai commented on JENKINS-36256 Re: "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity Success jenkins.war Failure - hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/war/2.14/jenkins.war (redirected to: http://ftp-chi.osuosl.org/pub/jenkins/war/2.14/jenkins.war) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1153) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1650) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketTimeoutException: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1105) ... 6 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source) at sun.net.www.http.HttpClient.parseHTTP(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source) at java.net.URLConnection.getHeaderFieldLong(Unknown Source) at java.net.URLConnection.getContentLengthLong(Unknown Source) at java.net.URLConnection.getContentLength(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1104) ... 6 more Add
[JIRA] (JENKINS-36257) Allow more the one shared workspace per job
Title: Message Title
Daniel Possamai updated an issue
Jenkins / JENKINS-36257
Allow more the one shared workspace per job
Change By:
Daniel Possamai
Problem: I need more the one shared workspace per jobSolution:For every configured shared workspace url, make available a unique system variable. Making this change will be possible to configure more the then one url per job. Today the plugin make available for a single job only the variable ${SHAREDSPACE_SCM_URL}.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36256) "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically
Title: Message Title Daniel Possamai updated an issue Jenkins / JENKINS-36256 "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically Change By: Daniel Possamai When I am trying to upgrade jenkins automatically I am getting the following error:hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/war/2.11/jenkins.war (redirected to: http://ftp-nyc.osuosl.org/pub/jenkins/war/2.11/jenkins.war)()Caused by: java.net.SocketTimeoutException: Read timed out---The proxy configuration is fine because I am able to update plugins. I belive I have timeout only when updting jenkins.war because of the size of the file. I notice this problem error since Jenkins version 1.6 ---Solution for the problem:I need a way to configure this timeout Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-36257) Allow more the one shared workspace per job
Title: Message Title
Daniel Possamai updated an issue
Jenkins / JENKINS-36257
Allow more the one shared workspace per job
Change By:
Daniel Possamai
Problem: I need more the one shared workspace per jobSolution:For every configured shared workspace url, make available a unique system variable. Making this change will be possible to configure more the one url per job.Today I have the plugin make available for a single job only the variable ${SHAREDSPACE_SCM_URL} available to use .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36257) Allow more the one shared workspace per job
Title: Message Title
Daniel Possamai created an issue
Jenkins / JENKINS-36257
Allow more the one shared workspace per job
Issue Type:
Improvement
Assignee:
Unassigned
Components:
shared-workspace-plugin
Created:
2016/Jun/28 2:16 AM
Environment:
shared-workspace-plugin version 1.0.2
Priority:
Minor
Reporter:
Daniel Possamai
Problem: I need more the one shared workspace per job Solution: For every configured shared workspace url, make available a unique system variable. Making this change will be possible to configure more the one url per job. Today I have only the variable $ {SHAREDSPACE_SCM_URL} available to use.
Add Comment
[JIRA] (JENKINS-36256) "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically
Title: Message Title Daniel Possamai updated an issue Jenkins / JENKINS-36256 "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically Change By: Daniel Possamai Environment: Windows 7 behind a proxy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36256) "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically
Title: Message Title Daniel Possamai created an issue Jenkins / JENKINS-36256 "java.net.SocketTimeoutException: Read timed out" error during jenkins upgrade automatically Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/28 1:34 AM Environment: Windows 7 behind a proxy Labels: proxy timeout upgrade automatically jenkins.war SocketTimeoutException Priority: Major Reporter: Daniel Possamai When I am trying to upgrade jenkins automatically I am getting the following error: hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/war/2.11/jenkins.war (redirected to: http://ftp-nyc.osuosl.org/pub/jenkins/war/2.11/jenkins.war) () Caused by: java.net.SocketTimeoutException: Read timed out --- The proxy configuration is fine because I am able to update plugins. I notice this problem since Jenkins version 1.6 --- Solution for the problem: I need a way to configure this timeout
[JIRA] [jira] (JENKINS-24990) JIRA Plugin is not linking in Jenkins for an issue in JIRA that starts with number
Daniel Possamai created JENKINS-24990 JIRA Plugin is not linking in Jenkins for an issue in JIRA that starts with number Issue Type: Bug Assignee: Unassigned Components: jira Created: 03/Oct/14 6:22 PM Description: If a JIRA issue key starts with a number, the link in Jenkins change log does not work. It only works for JIRA issue key that starts with a letter. Jira returns the following error: hudson.plugins.jira.JiraChangeLogAnnotator annotate INFO: No known JIRA project corresponding to id: 'AAA-' The original issue key is: 111AAA- Environment: jenkins_1580, JIRA plugin 1.39, Subversion Plugin 2.2 (configured to svn client 1.7) Project: Jenkins Labels: plugins jira Priority: Minor Reporter: Daniel Possamai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-24990) JIRA Plugin is not linking in Jenkins for an issue in JIRA that starts with number
Daniel Possamai assigned JENKINS-24990 to Daniel Possamai JIRA Plugin is not linking in Jenkins for an issue in JIRA that starts with number Change By: Daniel Possamai (03/Oct/14 8:11 PM) Assignee: DanielPossamai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-24990) JIRA Plugin is not linking in Jenkins for an issue in JIRA that starts with number
Daniel Possamai closed JENKINS-24990 as Fixed JIRA Plugin is not linking in Jenkins for an issue in JIRA that starts with number Not a bug, just a configuration problem Change By: Daniel Possamai (03/Oct/14 8:14 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-24990) JIRA Plugin is not linking in Jenkins for an issue in JIRA that starts with number
Daniel Possamai resolved JENKINS-24990 as Fixed JIRA Plugin is not linking in Jenkins for an issue in JIRA that starts with number In the plugin configuration change the field Isse Pattern FROM (default): (a-zA-Za-zA-Z0-9_+-1-90-9*)(^.|\.^0-9|\.$|$) TO: (a-zA-Z0-9_+-1-90-9*)(^.|\.^0-9|\.$|$) Change By: Daniel Possamai (03/Oct/14 8:13 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
