[JIRA] (JENKINS-52404) Job fails randomly when using copyArtifact
Title: Message Title ikedam updated JENKINS-52404 There’s no fundamental resolution for this issue as it comes from the OS level issue. And I don’t plan to add retry feature to copyartifact as it cause codes complicated and hard to maintain. Please consider workarounds like excluding scan directory, remove files in the target directory before copying, and so on. Jenkins / JENKINS-52404 Job fails randomly when using copyArtifact Change By: ikedam Status: Open Fixed but Unreleased Assignee: Marco Steffan Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-52552) Cloudbees folders do not work when using parameters
Title: Message Title ikedam updated JENKINS-52552 It sounds like a permission issue. Please have a look on https://wiki.jenkins.io/pages/viewpage.action?pageId=42470728#CopyArtifactPlugin-Specifyingprojectdynamically(withvariables) Jenkins / JENKINS-52552 Cloudbees folders do not work when using parameters Change By: ikedam Status: Open Fixed but Unreleased Assignee: Martin Cassidy Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit
[JIRA] (JENKINS-53366) `keep forever` is no longer inherit to sub configurations
Title: Message Title ikedam assigned an issue to Kohsuke Kawaguchi It looks rather an issue of matrix-project plugin. Please update this if you know from what version of matrix-project this issue happened. Jenkins / JENKINS-53366 `keep forever` is no longer inherit to sub configurations Change By: ikedam Summary: [CopyArtifact] fails when using latestSavedBuild selector from Multi-Configuration project `keep forever` is no longer inherit to sub configurations Component/s: matrix-project-plugin Component/s: copyartifact-plugin Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57224) Plugin Failed to Initialize after Jenkins restart
Title: Message Title ikedam updated JENKINS-57224 Actually, the root cause of this issue is unknown at last. It looks related to processing of Jenkins core in boot time, and cannot be reproduce in my environment. Though, I updated the implementation looking related to this issue in copyartifact-1.39 and should be fixed. https://github.com/jenkinsci/copyartifact-plugin/commit/946f9e47059cede6a6b50934f86efca42b574e05#diff-a1fdcd3da2dbec876fd20075be0d4108 You’re using a really old version of copyartifact, and please update to the latest and see the problem is resolved. Jenkins / JENKINS-57224 Plugin Failed to Initialize after Jenkins restart Change By: ikedam Status: Open Fixed but Unreleased Assignee: siva bora Resolution: Fixed Released As: copyartifact-1.39 Add Comment
[JIRA] (JENKINS-57241) Copy Artifact copying files when shouldn't and parameter filter errors
Title: Message Title ikedam updated JENKINS-57241 Though it’s really difficult to see what’s the actual problem you’re facing as your description is really long and looks describing unrelated things, it sounds that your problem is that “Copy Artifact is run unexpectedly though you’re expecting it’s controlled with parameter values”. You looks confuse the parameter filter feature of Copy Artifact plugin and the condition defined with Conditional Buildstep plugin and Run Condition plugin. The parameter filter feature of Copy Artifact plugin filters builds to copy from, and don’t skip the step itself. From the console output, Conditional Buildstep is applied to "Send build artifacts over SSH". Please reconfigure your project and put Copy Artifact under Conditional Buildstep. If that doesn’t resolve your problem, please reopen this ticked with information to how to reproduce the problem with least steps in a new Jenkins instance. Jenkins / JENKINS-57241 Copy Artifact copying files when shouldn't and parameter filter errors Change By: ikedam Status: Open Fixed but Unreleased Assignee: Kim Abbott Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman commented on JENKINS-57411 Re: Upgrade github-branch-source-plugin to use okhttp3 Josh Soref we are seeing that the periodic scans don't seem to be running periodically, and a branch whose name has been recycled (but for whom we'd expect github to send a notification) isn't being noticed automatically. We are able to use "Scan Repository Now" to pick up those branches, which feels like progress. Yeah, that's better than nothing. Take a look at the Events log for the org/repo to see if there are errors. Otherwise, errors might only show in the Jenkins Master's console log output. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199216.1557540525000.420.1557541380063%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Change By: Liam Newman The latest OkHttp (v2.7.5) is over three years old. The web has come a long way. There are a significant number of Jenkins JIRA and Zendesk issues related to using this ancient library in key plugins.We should upgrade Jenkins to use OkHttp3.NOTES:* OkHttp 2.x and 3.x exist and separate packages and can run side-by-side without conflict. However, different versions of 3.x may be incompatible if clients are using obsolete classes/methods.* OkHttp 3.12.2 is the last version that is reasonably compatible with 2.7.5. Upgrading will require some changes but not huge ones.* OkHttp 3.13.1 has some notable incompatibilities with 2.7.5, but also some better defaults.* OkHttp 3.14.1 removes UrlFactory which is a serious version-incompatible API change for several plugins.Early exploration of this upgrade was started to test whether it would address issues such ass JENKINS-54126. Finding so far while using 3.12.2:* okio v2.2.x is needed for okhttp3. * Some special class loading settings are needed to get the right versions okhttp3 and okio to be loaded.* (Last updated May 9, 2019):Please give this version of the plugin a try: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.3-rc841.52a0b90bff37/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Change By: Liam Newman The latest OkHttp (v2.7.5) is over three years old. The web has come a long way. There are a significant number of Jenkins JIRA and Zendesk issues related to using this ancient library in key plugins.We should upgrade Jenkins to use OkHttp3.NOTES:* OkHttp 2.x and 3.x exist and separate packages and can run side-by-side without conflict. However, different versions of 3.x may be incompatible if clients are using obsolete classes/methods.* OkHttp 3.12.2 is the last version that is reasonably compatible with 2.7.5. Upgrading will require some changes but not huge ones.* OkHttp 3.13.1 has some notable incompatibilities with 2.7.5, but also some better defaults.* OkHttp 3.14.1 removes UrlFactory which is a serious version-incompatible API change for several plugins. Early exploration of this upgrade was started to test whether it would address issues such ass JENKINS-54126. Finding so far while using 3.12.2:* okio v2.2.x is needed for okhttp3. * Some special class loading settings are needed to get the right versions okhttp3 and okio to be loaded.* Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Change By: Liam Newman The latest OkHttp (v2.7.5) is over three years old. The web has come a long way. There are a significant number of Jenkins JIRA and Zendesk issues related to using this ancient library in key plugins.We should upgrade Jenkins to use OkHttp3.NOTES:* OkHttp 2.x and 3.x exist and separate packages and can run side-by-side without conflict. However, different versions of 3.x may be incompatible if clients are using obsolete classes/methods.* OkHttp 3.12.2 is the last version that is reasonably compatible with 2.7.5. Upgrading will require some changes but not huge ones.* OkHttp 3.13.1 has some notable incompatibilities with 2.7.5, but also some better defaults.* OkHttp 3.14.1 removes UrlFactory which is a serious version-incompatible API change for several plugins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199216.1557540525000.417.1557540840059%40Atlassian.JIRA. For more
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Josh Soref Let's talk about an issues you see with okhttp3 version as a separate issue: https://issues.jenkins-ci.org/browse/JENKINS-57411 We sort of hijacked this issue as something that might be fixed by the okhttp3 upgrade. If you see this issue again, it should go here, if you see other issues that should go there. Sound good? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.352.1557540721432%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-05-11 02:08 Priority: Minor Reporter: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199216.1557540525000.349.1557540540108%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-51746) Job Import Plugin does not import jobs
Title: Message Title
Kim Abbott edited a comment on JENKINS-51746
Re: Job Import Plugin does not import jobs
Mark, what permissions did you need to add on the remote Jenkins? A colleague was attempting to use this plugin and was having same issue (nothing happened, no logs). I discovered that she had not been using the right credentials in the host Jenkins configuration. Once I fixed that, it finally started logging, but now I'm getting one of 2 errors, either: { \ {I/O exception (java.net.NoRouteToHostException) caught when processing request to {}->http://:8080: No route to host (Host unreachable)May 10, 2019 11:51:18 PM INFO org.apache.http.impl.execchain.RetryExec executeRetrying request to {}->http://:8080May 10, 2019 11:51:18 PM SEVERE org.jenkins.ci.plugins.jobimport.client.RestApiClient getRemoteItemsFailed to list job from remote http://:8080/java.net.NoRouteToHostException: No route to host (Host unreachable)}}With a long stack trace, or:{{Failed to list job from remote /java.net.MalformedURLException: no protocol: /api/xml?tree=jobs[name,url,description]}}With a long stack trace. I can ping the remote from the host, so I know it can "see" it.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191193.1528305493000.348.1557535260342%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51746) Job Import Plugin does not import jobs
Title: Message Title
Kim Abbott commented on JENKINS-51746
Re: Job Import Plugin does not import jobs
Mark, what permissions did you need to add on the remote Jenkins? A colleague was attempting to use this plugin and was having same issue (nothing happened, no logs). I discovered that she had not been using the right credentials in the host Jenkins configuration. Once I fixed that, it finally started logging, but now I'm getting one of 2 errors, either: {{I/O exception (java.net.NoRouteToHostException) caught when processing request to {}->http://:8080: No route to host (Host unreachable) May 10, 2019 11:51:18 PM INFO org.apache.http.impl.execchain.RetryExec execute Retrying request to {}->http://:8080 May 10, 2019 11:51:18 PM SEVERE org.jenkins.ci.plugins.jobimport.client.RestApiClient getRemoteItems Failed to list job from remote http://:8080/ java.net.NoRouteToHostException: No route to host (Host unreachable)}} With a long stack trace, or: {{Failed to list job from remote / java.net.MalformedURLException: no protocol: /api/xml?tree=jobs[name,url,description]}} With a long stack trace.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191193.1528305493000.343.1557535200971%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54723) EC2 Plugin: Include tags in created EBS volumes
Title: Message Title Camilo Silva edited a comment on JENKINS-54723 Re: EC2 Plugin: Include tags in created EBS volumes when are you planning to release this any soon ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195525.1542713511000.336.1557531180162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54723) EC2 Plugin: Include tags in created EBS volumes
Title: Message Title Camilo Silva commented on JENKINS-54723 Re: EC2 Plugin: Include tags in created EBS volumes are you planning to release this any soon? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195525.1542713511000.331.1557531120221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title Ryan Smith updated an issue Jenkins / JENKINS-57410 Splunk Plugin Causing threadlock When Testing Connections Change By: Ryan Smith Attachment: threads_before.out Attachment: threads_after.out Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199215.1557526135000.328.1557528360180%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title Seppo Yli-Olli edited a comment on JENKINS-50772 Re: Content type not set reasonably Even if you only populated content type for most common things (txt, html), this would still be useful. Is this being actively worked on? This limitation makes using HTML reports through Jenkins web UI quite painful if this plugin is active. My assumption based on what I've seen thus far is latter option is the right one but it could be that I'm just missing some details of presigned URL's. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189876.1523552257000.323.1557526380136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title Seppo Yli-Olli commented on JENKINS-50772 Re: Content type not set reasonably Even if you only populated content type for most common things (txt, html), this would still be useful. Is this being actively worked on? This limitation makes using HTML reports through Jenkins web UI quite painful if this plugin is active. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189876.1523552257000.317.1557526260339%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title
Ryan Smith updated an issue
Jenkins / JENKINS-57410
Splunk Plugin Causing threadlock When Testing Connections
Change By:
Ryan Smith
Filing on behalf of john.m...@viasat.com:We are using the Splunk Plugin for Jenkins 1.7.1 (latest).I am seeing some odd behavior that I would like to get some further feedback on please.In the configure system section there is a option to test the Splunk connection. If this is pressed several times it appears the the two splunkins-worker threads will become locked indefinitely until Jenkins is restarted (not sending any data to Splunk). Looking at netstat there are several sockets in CLOSE_WAIT to the Splunk HTTP input host.I am able to reproduce this at will within our test environment. It appears the test connection is using a call back to Jenkins for which we have NGINX in front. Once in this state additional attempts to test the connection fail due to a 504 timeout:Here is the NGINX log of interest:{code}2019/04/29 16:01:36 [error] 9051#9051: *831865 upstream prematurely closed connection while reading response header from upstream, client: 10.68.153.30, server: wdc1jenkinst01.hq.corp.viasat.com, request: "POST /descriptorByName/com.splunk.splunkjenkins.SplunkJenkinsInstallation/testHttpInput HTTP/1.1", upstream: "http://127.0.0.1:8080/descriptorByName/com.splunk.splunkjenkins.SplunkJenkinsInstallation/testHttpInput", host: "jenkins.test.viasat.com", referrer: "https://jenkins.test.viasat.com/configure"{code}Here is the netstat output as well: before Before : {code} Mon Apr 29 16:46:47 MDT 2019 [root@wdc1jenkinst01 ~]# netstat -ntap | grep java|grep :8088 tcp 0 0 10.68.154.134:35287 10.137.14.19:8088 ESTABLISHED 22706/java tcp 0 0 10.68.154.134:35291 10.137.14.19:8088 ESTABLISHED 22706/java{code} After: {code}date;netstat -natp|grep java|grep :8088 Mon Apr 29 16:52:33 MDT 2019 tcp 102 0 10.68.154.134:11909 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36547 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11895 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36207 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36569 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36581 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11925 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36575 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11885 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36529 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36531 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11919 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36553 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11915 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36519 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11901 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36541 10.137.14.19:8088 CLOSE_WAIT
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title
Ryan Smith updated an issue
Jenkins / JENKINS-57410
Splunk Plugin Causing threadlock When Testing Connections
Change By:
Ryan Smith
Filing on behalf of john.m...@viasat.com:We are using the Splunk Plugin for Jenkins 1.7.1 (latest).I am seeing some odd behavior that I would like to get some further feedback on please.In the configure system section there is a option to test the Splunk connection. If this is pressed several times it appears the the two splunkins-worker threads will become locked indefinitely until Jenkins is restarted (not sending any data to Splunk). Looking at netstat there are several sockets in CLOSE_WAIT to the Splunk HTTP input host.I am able to reproduce this at will within our test environment. It appears the test connection is using a call back to Jenkins for which we have NGINX in front. Once in this state additional attempts to test the connection fail due to a 504 timeout:Here is the NGINX log of interest:{code}2019/04/29 16:01:36 [error] 9051#9051: *831865 upstream prematurely closed connection while reading response header from upstream, client: 10.68.153.30, server: wdc1jenkinst01.hq.corp.viasat.com, request: "POST /descriptorByName/com.splunk.splunkjenkins.SplunkJenkinsInstallation/testHttpInput HTTP/1.1", upstream: "http://127.0.0.1:8080/descriptorByName/com.splunk.splunkjenkins.SplunkJenkinsInstallation/testHttpInput", host: "jenkins.test.viasat.com", referrer: "https://jenkins.test.viasat.com/configure"{code}Here is the netstat output as well:before: {code} Mon Apr 29 16:46:47 MDT 2019 [root@wdc1jenkinst01 ~]# netstat -ntap | grep java|grep :8088 tcp 0 0 10.68.154.134:35287 10.137.14.19:8088 ESTABLISHED 22706/java tcp 0 0 10.68.154.134:35291 10.137.14.19:8088 ESTABLISHED 22706/java {code} {code}{code}date;netstat -natp|grep java|grep :8088 Mon Apr 29 16:52:33 MDT 2019 tcp 102 0 10.68.154.134:11909 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36547 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11895 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36207 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36569 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36581 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11925 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36575 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11885 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36529 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36531 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11919 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36553 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11915 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36519 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11901 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36541 10.137.14.19:8088 CLOSE_WAIT 22706/java
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title Ryan Smith created an issue Jenkins / JENKINS-57410 Splunk Plugin Causing threadlock When Testing Connections Issue Type: Bug Assignee: Ted Components: splunk-devops-plugin Created: 2019-05-10 22:08 Environment: CloudBees Jenkins Enterprise 2.138.2.2-rollingSplunk Plugin for Jenkins 1.7.1 Labels: Splunk Priority: Minor Reporter: Ryan Smith Filing on behalf of john.m...@viasat.com: We are using the Splunk Plugin for Jenkins 1.7.1 (latest). I am seeing some odd behavior that I would like to get some further feedback on please. In the configure system section there is a option to test the Splunk connection. If this is pressed several times it appears the the two splunkins-worker threads will become locked indefinitely until Jenkins is restarted (not sending any data to Splunk). Looking at netstat there are several sockets in CLOSE_WAIT to the Splunk HTTP input host. I am able to reproduce this at will within our test environment. It appears the test connection is using a call back to Jenkins for which we have NGINX in front. Once in this state additional attempts to test the connection fail due to a 504 timeout: Here is the NGINX log of interest: 2019/04/29 16:01:36 [error] 9051#9051: *831865 upstream prematurely closed connection while reading response header from upstream, client: 10.68.153.30, server: wdc1jenkinst01.hq.corp.viasat.com, request: "POST
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title
Ryan Smith updated an issue
Jenkins / JENKINS-57410
Splunk Plugin Causing threadlock When Testing Connections
Change By:
Ryan Smith
Filing on behalf of john.m...@viasat.com:We are using the Splunk Plugin for Jenkins 1.7.1 (latest).I am seeing some odd behavior that I would like to get some further feedback on please.In the configure system section there is a option to test the Splunk connection. If this is pressed several times it appears the the two splunkins-worker threads will become locked indefinitely until Jenkins is restarted (not sending any data to Splunk). Looking at netstat there are several sockets in CLOSE_WAIT to the Splunk HTTP input host.I am able to reproduce this at will within our test environment. It appears the test connection is using a call back to Jenkins for which we have NGINX in front. Once in this state additional attempts to test the connection fail due to a 504 timeout:Here is the NGINX log of interest:{code:java}2019/04/29 16:01:36 [error] 9051#9051: *831865 upstream prematurely closed connection while reading response header from upstream, client: 10.68.153.30, server: wdc1jenkinst01.hq.corp.viasat.com, request: "POST /descriptorByName/com.splunk.splunkjenkins.SplunkJenkinsInstallation/testHttpInput HTTP/1.1", upstream: "http://127.0.0.1:8080/descriptorByName/com.splunk.splunkjenkins.SplunkJenkinsInstallation/testHttpInput", host: "jenkins.test.viasat.com", referrer: "https://jenkins.test.viasat.com/configure"{code:java}Here is the netstat output as well:before: {code :java } Mon Apr 29 16:46:47 MDT 2019 [root@wdc1jenkinst01 ~]# netstat -ntap | grep java|grep :8088 tcp 0 0 10.68.154.134:35287 10.137.14.19:8088 ESTABLISHED 22706/java tcp 0 0 10.68.154.134:35291 10.137.14.19:8088 ESTABLISHED 22706/java{code}{code :java }{code :java }date;netstat -natp|grep java|grep :8088 Mon Apr 29 16:52:33 MDT 2019 tcp 102 0 10.68.154.134:11909 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36547 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11895 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36207 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36569 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36581 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11925 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36575 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11885 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36529 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36531 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11919 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36553 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11915 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36519 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11901 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36541
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title
Ryan Smith updated an issue
Jenkins / JENKINS-57410
Splunk Plugin Causing threadlock When Testing Connections
Change By:
Ryan Smith
Filing on behalf of john.m...@viasat.com:We are using the Splunk Plugin for Jenkins 1.7.1 (latest).I am seeing some odd behavior that I would like to get some further feedback on please.In the configure system section there is a option to test the Splunk connection. If this is pressed several times it appears the the two splunkins-worker threads will become locked indefinitely until Jenkins is restarted (not sending any data to Splunk). Looking at netstat there are several sockets in CLOSE_WAIT to the Splunk HTTP input host.I am able to reproduce this at will within our test environment. It appears the test connection is using a call back to Jenkins for which we have NGINX in front. Once in this state additional attempts to test the connection fail due to a 504 timeout:Here is the NGINX log of interest:{code :java }2019/04/29 16:01:36 [error] 9051#9051: *831865 upstream prematurely closed connection while reading response header from upstream, client: 10.68.153.30, server: wdc1jenkinst01.hq.corp.viasat.com, request: "POST /descriptorByName/com.splunk.splunkjenkins.SplunkJenkinsInstallation/testHttpInput HTTP/1.1", upstream: "http://127.0.0.1:8080/descriptorByName/com.splunk.splunkjenkins.SplunkJenkinsInstallation/testHttpInput", host: "jenkins.test.viasat.com", referrer: "https://jenkins.test.viasat.com/configure"{code :java }Here is the netstat output as well:before: {code} Mon Apr 29 16:46:47 MDT 2019 [root@wdc1jenkinst01 ~]# netstat -ntap | grep java|grep :8088 tcp 0 0 10.68.154.134:35287 10.137.14.19:8088 ESTABLISHED 22706/java tcp 0 0 10.68.154.134:35291 10.137.14.19:8088 ESTABLISHED 22706/java{code}{code}{code}date;netstat -natp|grep java|grep :8088 Mon Apr 29 16:52:33 MDT 2019 tcp 102 0 10.68.154.134:11909 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36547 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11895 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36207 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36569 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36581 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11925 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36575 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11885 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36529 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36531 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11919 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36553 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11915 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36519 10.137.14.19:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:11901 10.137.14.79:8088 CLOSE_WAIT 22706/java tcp 102 0 10.68.154.134:36541 10.137.14.19:8088 CLOSE_WAIT
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title Ryan Smith updated an issue Jenkins / JENKINS-57410 Splunk Plugin Causing threadlock When Testing Connections Change By: Ryan Smith Environment: CloudBees Jenkins Enterprise 2.138.2.2- rollingSplunk rollingSplunk Plugin for Jenkins 1.7.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199215.1557526135000.308.1557526200242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57409) Content type not set when uploading artifacts
Title: Message Title Seppo Yli-Olli closed an issue as Duplicate Jenkins / JENKINS-57409 Content type not set when uploading artifacts Change By: Seppo Yli-Olli Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199214.1557525552000.304.1557526080081%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57409) Content type not set when uploading artifacts
Title: Message Title Seppo Yli-Olli created an issue Jenkins / JENKINS-57409 Content type not set when uploading artifacts Issue Type: Bug Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2019-05-10 21:59 Priority: Major Reporter: Seppo Yli-Olli When artifacts are uploaded to S3, content type is not set. This results in all files downloaded through Jenkins web UI to be treated as binary data which is quite bad as users may expect eg HTML reports to be directly viewable. Add Comment
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Devin Nusbaum updated JENKINS-57085 A fix for this issue was just released in Pipeline: Groovy 2.68. Jenkins / JENKINS-57085 Stack Traces with complex file names cannot be deserialized by XStream Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps 2.68, groovy-cps 1.27 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Devin Nusbaum updated JENKINS-54186 A fix for this issue was just released in Pipeline: Groovy 2.68. Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: workflow-cps 2.68 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194817.1540223284000.226.1557520023480%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Josh Soref commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub So, we aren't currently hitting the ‘Jenkinsfile’ not found problem, but we are seeing that the periodic scans don't seem to be running periodically, and a branch whose name has been recycled (but for whom we'd expect github to send a notification) isn't being noticed automatically. We are able to use "Scan Repository Now" to pick up those branches, which feels like progress. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.157.1557519481362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57408) MSBuild plugin "Install automatically" function not working
Title: Message Title Steven Lee updated an issue Jenkins / JENKINS-57408 MSBuild plugin "Install automatically" function not working Change By: Steven Lee Environment: Operating Systems: Master - CentOS Linux release 7.2.1511Windows slave node - Windows Server 2012 RS Standard 64-bitLogs - No activity captured in var/log/jenkins/jenkins.logJenkins version: ver.2.164.1Installed Plugins:Active Directory plugin - 2.12Analysis Model API Plug-in - 4.0.0AnsiColor - 0.6.2Ant Plugin - 1.9Any Build Step Plugin - 0.1Apache HttpComponents Client 4.x API Plugin - 4.5.5-3.0Artifactory Plugin - 3.2.1Authentication Tokens API Plugin - 1.3Autofavorite for Blue Ocean - 1.2.3Bitbucket Branch Source Plugin - 2.4.2Bitbucket Build Status Notifier Plugin - 1.4.1Bitbucket Pipeline for Blue Ocean - 1.13.2Stash Notifier - 1.17Black Duck Hub Plugin - 4.0.0Blue Ocean - 1.13.2Blue Ocean Core JS - 1.13.2Blue Ocean Executor Info - 1.13.2Blue Ocean Pipeline Editor - 1.13.2bouncycastle API Plugin - 2.17Branch API Plugin - 2.2.0Build Blocker Plugin - 1.7.3Build Timeout - 1.19built-on-column - 1.1Command Agent Launcher Plugin - 1.3Common API for Blue Ocean - 1.13.2Conditional BuildStep - 1.3.6Config API for Blue Ocean - 1.13.2Config File Provider Plugin - 3.6Copy Artifact Plugin - 1.42Credentials Binding Plugin - 1.18Credentials Plugin - 2.1.18Cucumber json test reporting. - 0.10.1Cucumber reports - 4.5.0CVS Plug-in - 2.14Dashboard for Blue Ocean - 1.13.2description setter plugin - 1.10Design Language - 1.13.2Display URL API - 2.3.1Display URL for Blue Ocean - 2.2.0Docker Commons Plugin - 1.13Docker Pipeline - 1.17Durable Task Plugin - 1.29elastic-axis - 1.2Email Extension Plugin - 2.66EnvInject API Plugin - 1.5Environment Injector Plugin - 2.1.6Events API for Blue Ocean - 1.13.2Extended Read Permission Plugin - 2.0External Monitor Job Type Plugin - 1.7EZ Templates - 1.3.2Favorite - 2.3.2FindBugs Plug-in - 5.0.0Flexible Publish Plugin - 0.15.2Folders Plugin - 6.7Git plugin - 3.9.3Git client plugin - 2.7.6Git Pipeline for Blue Ocean - 1.13.2GIT server Plugin - 1.7GitHub API Plugin - 1.95GitHub Branch Source Plugin - 2.4.5GitHub Organization Folder Plugin - 1.6GitHub Pipeline for Blue Ocean - 1.13.2GitHub plugin - 1.29.4Gradle Plugin - 1.31Green Balls - 1.15Groovy - 2.2Handy Uri Templates 2.x API Plugin - 2.1.7-1.0HTML Publisher plugin - 1.18i18n for Blue Ocean - 1.13.2Icon Shim Plugin - 2.0.3InfluxDB Plugin - 1.20.4Ivy Plugin - 2.0Jackson 2 API Plugin - 2.9.8JaCoCo plugin - 3.0.4Javadoc Plugin - 1.5_javascript_ GUI Lib: ACE Editor bundle plugin - 1.1_javascript_ GUI Lib: Handlebars bundle plugin - 1.1.1_javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1_javascript_ GUI Lib: Moment.js bundle plugin - 1.1.1JAXB plugin - 2.3.0.1JDK Tool Plugin - 1.2JIRA plugin - 3.0.5JIRA Integration for Blue Ocean - 1.13.2JSch dependency plugin - 0.1.55JUnit Plugin - 1.27JWT for Blue Ocean - 1.13.2LDAP Plugin - 1.20Lockable Resources plugin - 2.5Logstash - 2.3.0Mailer Plugin - 1.23MapDB API Plugin - 1.0.9.0Mask Passwords Plugin - 2.12.0Matrix Authorization Strategy Plugin - 2.3Matrix Project Plugin - 1.14Maven Integration plugin - 3.2Mercurial plugin - 2.5Metrics Plugin - 4.0.2.3Monitoring - 1.76.0MSBuild Plugin - 1.29Multijob plugin -
[JIRA] (JENKINS-57073) Linebreak between JobName and BuildName
Title: Message Title Gustaf Lundh closed an issue as Fixed In 1.8 Jenkins / JENKINS-57073 Linebreak between JobName and BuildName Change By: Gustaf Lundh Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198816.1555483248000.152.1557519240568%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57408) MSBuild plugin "Install automatically" function not working
Title: Message Title Steven Lee updated an issue Jenkins / JENKINS-57408 MSBuild plugin "Install automatically" function not working Change By: Steven Lee Summary: MSBuild plugin "Install automatically" functionnot working Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199211.1557518699000.154.1557519360117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57073) Linebreak between JobName and BuildName
Title: Message Title Gustaf Lundh started work on JENKINS-57073 Change By: Gustaf Lundh Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198816.1555483248000.148.1557519240511%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57073) Linebreak between JobName and BuildName
Title: Message Title Gustaf Lundh resolved as Fixed Jenkins / JENKINS-57073 Linebreak between JobName and BuildName Change By: Gustaf Lundh Status: In Progress Resolved Resolution: Fixed Released As: 1.8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198816.1555483248000.150.1557519240539%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57258) Lost builds historical data after updating to Jenkins v2.175
Title: Message Title Daniel Beck commented on JENKINS-57258 Re: Lost builds historical data after updating to Jenkins v2.175 Does this problem still occur with Jenkins 2.176? I assume instances were restored from backup when this happened, so what happens when you skip 2.175? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199022.1556633695000.139.1557518940206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57408) MSBuild plugin "Install automatically" function
Title: Message Title sleem anar created an issue Jenkins / JENKINS-57408 MSBuild plugin "Install automatically" function Issue Type: Bug Assignee: Lionel Cabasson Components: msbuild-plugin Created: 2019-05-10 20:04 Environment: Operating Systems: Master - CentOS Linux release 7.2.1511 Windows slave node - Windows Server 2012 RS Standard 64-bit Logs - No activity captured in var/log/jenkins/jenkins.log Jenkins version: ver.2.164.1 Installed Plugins: Active Directory plugin - 2.12 Analysis Model API Plug-in - 4.0.0 AnsiColor - 0.6.2 Ant Plugin - 1.9 Any Build Step Plugin - 0.1 Apache HttpComponents Client 4.x API Plugin - 4.5.5-3.0 Artifactory Plugin - 3.2.1 Authentication Tokens API Plugin - 1.3 Autofavorite for Blue Ocean - 1.2.3 Bitbucket Branch Source Plugin - 2.4.2 Bitbucket Build Status Notifier Plugin - 1.4.1 Bitbucket Pipeline for Blue Ocean - 1.13.2 Stash Notifier - 1.17 Black Duck Hub Plugin - 4.0.0 Blue Ocean - 1.13.2 Blue Ocean Core JS - 1.13.2 Blue Ocean Executor Info - 1.13.2 Blue Ocean Pipeline Editor - 1.13.2 bouncycastle API Plugin - 2.17 Branch API Plugin - 2.2.0 Build Blocker Plugin - 1.7.3 Build Timeout - 1.19 built-on-column - 1.1 Command Agent Launcher Plugin - 1.3 Common API for Blue Ocean - 1.13.2 Conditional BuildStep - 1.3.6 Config API for Blue Ocean - 1.13.2 Config File Provider Plugin - 3.6 Copy Artifact Plugin - 1.42 Credentials Binding Plugin - 1.18 Credentials Plugin - 2.1.18 Cucumber json test reporting. - 0.10.1 Cucumber reports - 4.5.0 CVS Plug-in - 2.14 Dashboard for Blue Ocean - 1.13.2 description setter plugin - 1.10 Design Language - 1.13.2 Display URL API - 2.3.1 Display URL for Blue Ocean - 2.2.0 Docker Commons Plugin - 1.13 Docker Pipeline - 1.17 Durable Task Plugin - 1.29 elastic-axis - 1.2 Email Extension Plugin - 2.66 EnvInject API Plugin - 1.5 Environment Injector Plugin - 2.1.6 Events API for Blue Ocean - 1.13.2 Extended Read Permission Plugin - 2.0 External Monitor Job Type Plugin - 1.7 EZ Templates - 1.3.2 Favorite - 2.3.2 FindBugs Plug-in - 5.0.0 Flexible Publish Plugin - 0.15.2 Folders Plugin - 6.7 Git plugin - 3.9.3 Git client plugin - 2.7.6 Git Pipeline for Blue Ocean - 1.13.2 GIT server Plugin - 1.7 GitHub API Plugin - 1.95 GitHub Branch Source Plugin - 2.4.5 GitHub Organization Folder Plugin - 1.6 GitHub Pipeline for Blue Ocean - 1.13.2 GitHub plugin - 1.29.4 Gradle Plugin - 1.31 Green Balls - 1.15 Groovy - 2.2 Handy Uri Templates 2.x API Plugin - 2.1.7-1.0 HTML Publisher plugin - 1.18 i18n for Blue Ocean - 1.13.2 Icon Shim Plugin - 2.0.3 InfluxDB Plugin - 1.20.4 Ivy
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Devin Nusbaum started work on JENKINS-56890 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198561.1554419267000.112.1557518283928%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-56890 IOException: "cannot find current thread" Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198561.1554419267000.89.1557518283453%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Devin Nusbaum updated JENKINS-56890 Jenkins / JENKINS-56890 IOException: "cannot find current thread" Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198561.1554419267000.114.1557518283955%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
yes Yes that is in my {{-Dno.Proxy kubernetes.default.svc,...}} that starts Jenkins .{{APISERVER=https://kubernetes.default.svc}} in the curl command.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.63.1557515100226%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API yes that is in my -Dno.Proxy kubernetes.default.svc,... that starts Kenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.55.1557514861397%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
yes that is in my {{-Dno.Proxy kubernetes.default.svc,...}} that starts Kenkins Jenkins
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.57.1557514861462%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Carlos Sanchez commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API so you don't want https://kubernetes.default.svc to go through the proxy, correct? do you have -Dno.Proxy=kubernetes.default.svc,somethingelse ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.47.1557514740183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Yeah been there looked at that also.I am now running Jenkins using the following java properties:{code:java}-Dhttp.proxy=http://x.x.x.x: -Dhttps.proxy=https://x.x.x.x: -Dno.Proxy=xxx -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort= -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort= -Dhttp.nonProxyHosts=xxx{code}Testing the connection from the Jenkins server running in Kubernetes through the Kubernetes plugin using the 'test connection' results in:{code:java}Error testing connection https://kubernetes.default: java.io.IOException: Unexpected response code for CONNECT: 502{code}and the following log entry on the proxy server:{code:bash}1557513166.881 67 192.168.1.73 TCP_TUNNEL/502 0 CONNECT kubernetes.default.svc:443 - FIRSTUP_PARENT/192.168.1.100 -{code}Testing the connection from the Jenkins server running in Kubernetes through the 'Manage Jenkins->Manage Plugins->Advanced' tab using the 'validate proxy' button with the test URL of 'https://kubernetes.default.svc' results in the following expected failure since we are not authenticated:{code:java}Failed to connect to https://kubernetes.default.svc.javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(SSLProtocolSocketFactory.java:257) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:115) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:156) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330){code}From the command line of the same Jenkins server that has the exact same proxy settings defined in the java properties above set in environment variables. I can issue the following and retrieve a json object containing all pods in the namespace:{code:bash}curl $APISERVER/api/v1/namespaces/pd-dgames-test/pods/ --header "Authorization: Bearer $TOKEN" --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt{code}Kubernetes plugin spinning up a slave repeatedly gives me this:{code:java}May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionWARNING: Failed to count the # of live instances on Kubernetesjava.io.IOException: Unexpected response code for CONNECT: 502at okhttp3.internal.connection.RealConnection.createTunnel(RealConnection.java:389)at okhttp3.internal.connection.RealConnection.connectTunnel(RealConnection.java:211)at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:152)at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:256)at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:134)at
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Yeah been there looked at that also.I am now running Jenkins using the following java properties:{code:java}-Dhttp.proxy=http://x.x.x.x: -Dhttps.proxy=https://x.x.x.x: -Dno.Proxy=xxx -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort= -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort= -Dhttp.nonProxyHosts=xxx{code}Testing the connection from the Jenkins server running in Kubernetes through the Kubernetes plugin using the 'test connection' results in:{code:java}Error testing connection https://kubernetes.default: java.io.IOException: Unexpected response code for CONNECT: 502{code}and the following log entry on the proxy server:{code:bash}1557513166.881 67 192.168.1.73 TCP_TUNNEL/502 0 CONNECT kubernetes.default.svc:443 - FIRSTUP_PARENT/192.168.1.100 -{code}Testing the connection from the Jenkins server running in Kubernetes through the 'Manage Jenkins->Manage Plugins->Advanced' tab using the 'validate proxy ' button with the test URL of 'https://kubernetes.default.svc' results in the following expected failure since we are not authenticated:{code:java}Failed to connect to https://kubernetes.default.svc.javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(SSLProtocolSocketFactory.java:257) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:115) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:156) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330){code}From the command line of the same Jenkins server that has the exact same proxy settings defined in the java properties above set in environment variables. I can issue the following and retrieve a json object containing all pods in the namespace:{code:bash}curl $APISERVER/api/v1/namespaces/pd-dgames-test/pods/ --header "Authorization: Bearer $TOKEN" --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt{code}Kubernetes plugin spinning up a slave repeatedly gives me this:{code:java}May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionWARNING: Failed to count the # of live instances on Kubernetesjava.io.IOException: Unexpected response code for CONNECT: 502at okhttp3.internal.connection.RealConnection.createTunnel(RealConnection.java:389)at okhttp3.internal.connection.RealConnection.connectTunnel(RealConnection.java:211)at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:152)at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:256)at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:134)at
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title Dax Games commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API I am now running Jenkins using the following java properties: -Dhttp.proxy=http://x.x.x.x: -Dhttps.proxy=https://x.x.x.x: -Dno.Proxy=xxx -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort= -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort= -Dhttp.nonProxyHosts=xxx Testing the connection from the Jenkins server running in Kubernetes through the Kubernetes plugin using the 'test connection' results in: Error testing connection https://kubernetes.default: java.io.IOException: Unexpected response code for CONNECT: 502 and the following log entry on the proxy server: 1557513166.881 67 192.168.1.73 TCP_TUNNEL/502 0 CONNECT kubernetes.default.svc:443 - FIRSTUP_PARENT/192.168.1.100 - Testing the connection from the Jenkins server running in Kubernetes through the 'Manage Jenkins->Manage Plugins->Advanced' tab using the 'validate proxy button with the test URL of 'https://kubernetes.default.svc' results in the following expected failure since we are not authenticated: Failed to connect to https://kubernetes.default.svc. javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(SSLProtocolSocketFactory.java:257) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:115) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:156) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330) From the command line of the same Jenkins server that has the exact same proxy settings defined in the java properties above set in environment variables. I can issue the following and retrieve a json object containing all pods in the namespace:
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title
Dax Games edited a comment on JENKINS-55123
Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Yeah been there looked at that also. I am now running Jenkins using the following java properties:{code:java}-Dhttp.proxy=http://x.x.x.x: -Dhttps.proxy=https://x.x.x.x: -Dno.Proxy=xxx -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort= -Dhttps.proxyHost=x.x.x.x -Dhttps.proxyPort= -Dhttp.nonProxyHosts=xxx{code}Testing the connection from the Jenkins server running in Kubernetes through the Kubernetes plugin using the 'test connection' results in:{code:java}Error testing connection https://kubernetes.default: java.io.IOException: Unexpected response code for CONNECT: 502{code}and the following log entry on the proxy server:{code:bash}1557513166.881 67 192.168.1.73 TCP_TUNNEL/502 0 CONNECT kubernetes.default.svc:443 - FIRSTUP_PARENT/192.168.1.100 -{code}Testing the connection from the Jenkins server running in Kubernetes through the 'Manage Jenkins->Manage Plugins->Advanced' tab using the 'validate proxy button with the test URL of 'https://kubernetes.default.svc' results in the following expected failure since we are not authenticated:{code:java}Failed to connect to https://kubernetes.default.svc.javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:450) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.verifyHostName(SSLProtocolSocketFactory.java:257) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:115) at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:156) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:714) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:394) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:178) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:404) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:330){code}From the command line of the same Jenkins server that has the exact same proxy settings defined in the java properties above set in environment variables. I can issue the following and retrieve a json object containing all pods in the namespace:{code:bash}curl $APISERVER/api/v1/namespaces/pd-dgames-test/pods/ --header "Authorization: Bearer $TOKEN" --cacert /var/run/secrets/kubernetes.io/serviceaccount/ca.crt{code}Kubernetes plugin spinning up a slave repeatedly gives me this:{code:java}May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 10, 2019 6:24:53 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionWARNING: Failed to count the # of live instances on Kubernetesjava.io.IOException: Unexpected response code for CONNECT: 502at okhttp3.internal.connection.RealConnection.createTunnel(RealConnection.java:389)at okhttp3.internal.connection.RealConnection.connectTunnel(RealConnection.java:211)at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:152)at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:256)at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:134)at
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman commented on JENKINS-57371 Re: error message when building PR Brandon Le Sann Ignoring this error message and merging the PR solved the issue and doesn't seem to appear again... What do you mean here? Once you merge one PR the rest of the PRs work okay from then on? Could you be a bit more specific? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.24.1557512220157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57394) Rename JDK Tool Plugin to Oracle JDK Installer plugin
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-57394 Rename JDK Tool Plugin to Oracle JDK Installer plugin Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199176.1557477158000.4.1557509280206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57395) Create administrative monitor to warn users about Oracle JDK Installer concerns
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-57395 Create administrative monitor to warn users about Oracle JDK Installer concerns Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199177.1557477277000.2.1557509221682%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57404) Jenkins Pipeline: exception when running post action
Title: Message Title Andreas Zeiler updated JENKINS-57404 Sorry for this Issue... I did not notice that I somehow installed an very old "Warnings-NG" Plugin. I tried a newer once... Issue fixed Jenkins / JENKINS-57404 Jenkins Pipeline: exception when running post action Change By: Andreas Zeiler Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199188.1557489065000.23467.1557493020137%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57372) Build Time is incorrect
Title: Message Title Hao CHEN resolved as Not A Defect Make sure the date time is correct in the host OS, then check the date time settings in pref Jenkins / JENKINS-57372 Build Time is incorrect Change By: Hao CHEN Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199153.1557322114000.23466.1557492420175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57407) Reached the email sending limit (500) for MailTrap
Title: Message Title
Ildefonso Montero updated an issue
Jenkins / JENKINS-57407
Reached the email sending limit (500) for MailTrap
Change By:
Ildefonso Montero
Seems that there exist some tests related with third party mailer system that are broken at acceptance-test-harness:{noformat}plugins.EmailExtPluginTest.buildplugins.MailWatcherPluginTest.notify_master_on_jenkins_restartplugins.MailWatcherPluginTest.notify_slave_on_restartplugins.MailerPluginTest.send_mail_for_failed_buildplugins.MailerPluginTest.send_test_mailplugins.MavenPluginTest.send_mail{noformat}So, seems a new credential token at MailTrap is needed as done here:https://github.com/jenkinsci/acceptance-test-harness/pull/439/filesAPI said it is owned by [~olivergondza]: {noformat}{ "id": 5560, "email": "ogon...@gmail.com", "api_token": "ceb98fc6d89ea0cf44e368916cec41c7", "auth_token": "eyJhbGciOiJIUzUxMiJ9 . eyJkYXRhIjp7InRva2VuIjoiY2ViOThmYzZkODllYTBjZjQ0ZTM2ODkxNmNlYzQxYzcifX0 . aTn0tZwmZlRm9s_82n5XEG2T_FjuNnqKKJzNLAZXNHeR90PKngyBvXUKXQja2wc2pG1omn2nKwforxJzSSqiig", "timezone": "UTC", "billing_plan_info": { "name": "Free", "need_card": false, "braintree_id": "", "price": 0, "companies_count": 1, "inboxes_count": 1, "messages_count": 50, "forward_rules_count": 0, "inbox_forward_email_count": 0, "company_users_count": 0, "inbox_users_count": 0, "inbox_rate_limit": 2, "inbox_email_address": false, "cycle_messages_count": 500, "cycle_forward_count": 0, "id": "unpaid" }, "billing_settings": null, "name": "ogondza", "gravatar_icon": "https://secure . gravatar.com/avatar/34d86e5da885fe60bfb18286fc71663e?s=100 https://secure.gravatar.com/avatar/34d86e5da885fe60bfb18286fc71663e?s=100 " , "gravatar_little_icon": "https://secure.gravatar.com/avatar/34d86e5da885fe60bfb18286fc71663e?s=30https://secure.gravatar.com/avatar/34d86e5da885fe60bfb18286fc71663e?s=30", "is_integrated": false, "timezone_in_int": 0, "pending_email": null, "billing_subscription_status": "active", "created_at_int": 1396535754, "providers": [ { "id": 80364, "provider": "google_oauth2", "created_at": "2018-03-08T12:14:17.150Z", "updated_at": "2018-03-08T12:14:17.150Z" } ], " system_message": "You have reached the email sending limit (500) for the current billing period. To resolve the matter, you may wait until the next billing period or upgrade your plan", "just_signed_up": false}{noformat}"You have reached the email sending limit (500) for the current billing period. To resolve the matter, you may wait until the next billing period or upgrade your plan" seems the issue here.
[JIRA] (JENKINS-57372) Build Time is incorrect
Title: Message Title Hao CHEN commented on JENKINS-57372 Re: Build Time is incorrect The time in this section has nothing to do with this plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199153.1557322114000.23462.1557492300470%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57407) Reached the email sending limit (500) for MailTrap
Title: Message Title
Ildefonso Montero created an issue
Jenkins / JENKINS-57407
Reached the email sending limit (500) for MailTrap
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
acceptance-test-harness
Created:
2019-05-10 12:44
Priority:
Minor
Reporter:
Ildefonso Montero
Seems that there exist some tests related with third party mailer system that are broken at acceptance-test-harness:
plugins.EmailExtPluginTest.build
plugins.MailWatcherPluginTest.notify_master_on_jenkins_restart
plugins.MailWatcherPluginTest.notify_slave_on_restart
plugins.MailerPluginTest.send_mail_for_failed_build
plugins.MailerPluginTest.send_test_mail
plugins.MavenPluginTest.send_mail
So, seems a new credential token at MailTrap is needed as done here: https://github.com/jenkinsci/acceptance-test-harness/pull/439/files API said it is owned by Oliver Gondža:
{
"id": 5560,
"email": "ogon...@gmail.com",
"api_token": "ceb98fc6d89ea0cf44e368916cec41c7",
"auth_token": "eyJhbGciOiJIUzUxMiJ9.eyJkYXRhIjp7InRva2VuIjoiY2ViOThmYzZkODllYTBjZjQ0ZTM2ODkxNmNlYzQxYzcifX0.aTn0tZwmZlRm9s_82n5XEG2T_FjuNnqKKJzNLAZXNHeR90PKngyBvXUKXQja2wc2pG1omn2nKwforxJzSSqiig",
"timezone": "UTC",
"billing_plan_info": {
"name": "Free",
"need_card": false,
"braintree_id": "",
"price": 0,
"companies_count": 1,
"inboxes_count": 1,
"messages_count": 50,
"forward_rules_count": 0,
"inbox_forward_email_count": 0,
"company_users_count": 0,
"inbox_users_count": 0,
"inbox_rate_limit": 2,
"inbox_email_address": false,
"cycle_messages_count":
[JIRA] (JENKINS-57397) Jenkins Build fails with “java.lang.NullPointerException”
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57397 Jenkins Build fails with “java.lang.NullPointerException” Change By: Mark Waite Component/s: workflow-cps-global-lib-plugin Component/s: git-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199180.1557480564000.23452.1557491580275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53259) Jenkins Pipeline build fails when trying to jenkins docker plugin
Title: Message Title
Chris Maes edited a comment on JENKINS-53259
Re: Jenkins Pipeline build fails when trying to jenkins docker plugin
I am trying to run the docker process on another server (not on Jenkins master); something like this:{code:java}node('master') { withDockerServer([uri: 'tcp://docker-server:4243']) { withDockerContainer([image: 'alpine']) { sh "pwd" } } }{code}this fails with the exact same error. Inspired by [https://github.com/jenkinsci/docker/issues/626#issuecomment-358331311] I have to use this workaround: * add docker-server as a jenkins slave * mount the /home directory of my jenkins user inside the docker. My Jenkinsfile now looks like this:{code:java}node('docker-server') { withDockerContainer([image: 'alpine', args: '-v /home/jenkins/:/home/jenkins']) { sh "pwd; ls /usr/local/bin" } }{code} it is just sad that I need to add the docker-server as a node...Another major drawback * for scripted pipeline : this workaround does not work with declarative syntax: {code:java}pipeline { agent { node { label 'docker-server' } } any stages { stage('test run on docker') { agent { docker { label 'docker-host' image 'alpine' args '-v /home/jenkins:/home/jenkins' } } steps { sh "pwd" } } } }{code} trouble it is jenkins master tries just sad that I need to launch add the docker agent himself now, and not on the *docker -server * as a node...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title ice zeng commented on JENKINS-54209 Re: Can't read file: Can't access the file it doesn't work by using custom workspace and install https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fcppcheck-plugin/detail/PR-46/2/artifacts/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194846.154031736.23443.1557491340187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57397) Jenkins Build fails with “java.lang.NullPointerException”
Title: Message Title Mark Waite commented on JENKINS-57397 Re: Jenkins Build fails with “java.lang.NullPointerException” We need either enough instructions to duplicate the problem or enough stack traces to identify the problem without duplicating it. Since the git plugin does not suppress exceptions, I'm reasonably confident that the issue is not in the git plugin. I suspect the exception is being thrown in the workflow CPS global lib plugin. That is the plugin which handles pipeline shared libraries. Have you made recent changes in the pipeline shared libraries that you are using? For example, if one of the shared libraries is causing a null pointer exception in its own code, that might cause the type of message you're seeing. I'll assign this to workflow-cps-global-lib plugin as a possible place for further investigation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199180.1557480564000.23450.1557491580252%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53259) Jenkins Pipeline build fails when trying to jenkins docker plugin
Title: Message Title
Chris Maes edited a comment on JENKINS-53259
Re: Jenkins Pipeline build fails when trying to jenkins docker plugin
I am trying to run the docker process on another server (not on Jenkins master); something like this:{code:java}node('master') { withDockerServer([uri: 'tcp://docker-server:4243']) { withDockerContainer([image: 'alpine']) { sh "pwd" } } }{code}this fails with the exact same error. Inspired by [https://github.com/jenkinsci/docker/issues/626#issuecomment-358331311] I have to use this workaround: * add docker-server as a jenkins slave * mount the /home directory of my jenkins user inside the docker. My Jenkinsfile now looks like this:{code:java}node('docker-server') { withDockerContainer([image: 'alpine', args: '-v /home/jenkins/:/home/jenkins']) { sh "pwd; ls /usr/local/bin" } }{code}it is just sad that I need to add the docker-server as a node... Another major drawback: this workaround does not work with declarative syntax: {code:java}pipeline { agent { node { label 'docker-server' } } stages { stage('test run on docker') { agent { docker { image 'alpine' args '-v /home/jenkins:/home/jenkins' } } steps { sh "pwd" } } } }{code}trouble is jenkins master tries to launch the docker agent himself now, and not on the *docker-server* node...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To
[JIRA] (JENKINS-57397) Jenkins Build fails with “java.lang.NullPointerException”
Title: Message Title Adharsh M commented on JENKINS-57397 Re: Jenkins Build fails with “java.lang.NullPointerException” Jenkins Log has the following entry : WARNING: Unexpected exception in CPS VM thread: CpsFlowExecution[Ownerprestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1/9470:[prestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1] #9470] java.lang.NullPointerException May 09, 2019 4:03:41 AM org.jenkinsci.plugins.workflow.job.WorkflowRun copyLogs WARNING: no such node 3 May 09, 2019 4:03:41 AM org.jenkinsci.plugins.workflow.job.WorkflowRun copyLogs WARNING: no such node 47 May 09, 2019 4:03:41 AM org.jenkinsci.plugins.workflow.job.WorkflowRun finish INFO: prestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1 #9470 completed: FAILURE May 09, 2019 4:03:42 AM org.jenkinsci.plugins.workflow.job.WorkflowRun finish INFO: prestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1 #9470 completed: SUCCESS May 09, 2019 4:03:43 AM org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregister WARNING: Ownerprestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1/9470:prestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1 #9470 was not in the list to begin with: [Ownerprestaging-falcon-unit-integration-acceptance-tests-backend-pullrequest-pipeline/15804:prestaging-falcon-unit-integration-acceptance-tests-backend-pullrequest-pipeline #15804, Ownerprestaging-falcon-unit-integration-acceptance-tests-backend-pullrequest-pipeline/15805:prestaging-falcon-unit-integration-acceptance-tests-backend-pullrequest-pipeline #15805, Ownerprestaging-falcon-unit-integration-acceptance-tests-backend-pullrequest-pipeline/15809:prestaging-falcon-unit-integration-acceptance-tests-backend-pullrequest-pipeline #15809, Ownerprestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1/9471:prestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1 #9471, Ownerprestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1/9472:prestaging-falcon-unit-integration-acceptance-tests-frontend-pullrequest-pipeline-1 #9472, Ownerprestaging-falcon-unit-integration-acceptance-tests-backend-pullrequest-pipeline/16124:prestaging-falcon-unit-integration-acceptance-tests-backend-pullrequest-pipeline #16124] May 09, 2019 4:03:51 AM org.jenkinsci.plugins.ghprb.GhprbRootAction handleAction Add Comment
[JIRA] (JENKINS-57397) Jenkins Build fails with “java.lang.NullPointerException”
Title: Message Title Adharsh M commented on JENKINS-57397 Re: Jenkins Build fails with “java.lang.NullPointerException” Let me know what else is needed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199180.1557480564000.23433.1557491100157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57406) credentials plugin user guide is system-centric rather than user-centric
Title: Message Title Dan Davies Brackett created an issue Jenkins / JENKINS-57406 credentials plugin user guide is system-centric rather than user-centric Issue Type: Improvement Assignee: Unassigned Components: credentials-plugin Created: 2019-05-10 12:22 Environment: I am reading the Jenkins credentials plugin user guide to try to understand an issue I'm having with my Jenkins setup, and I am finding it extremely frustrating. The guide is written by someone(s?) who obviously understand the credentials plugin well, and the motivation behind it; unfortunately, it assumes that I want or need to understand everything about the plugin in order to do anything with it. I just want to use the thing, not learn the whys and wherefores of its creation. It has no internal links to facilitate navigation around the document; section headers are difficult to find while scrolling; detailed step-by-step screenshots are put next to overviews. Priority: Minor Reporter: Dan Davies Brackett Add Comment
[JIRA] (JENKINS-57269) Declarative pipeline with ssh-steps-plugin
Title: Message Title Davide F commented on JENKINS-57269 Re: Declarative pipeline with ssh-steps-plugin Hello, Do you have any update regarding this support request ? Best regards Davide Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199035.1556696089000.23425.1557490800272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Vi Pl updated an issue Jenkins / JENKINS-57121 list view jobnames is missing getter and setter for jcasc compliance Change By: Vi Pl Attachment: image-2019-05-10-14-19-39-495.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198871.1555696084000.23427.1557490800297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Vi Pl commented on JENKINS-57121 Re: list view jobnames is missing getter and setter for jcasc compliance @Joseph Petersen Are you sure this is a problem? I managed to create a new list view with: jenkins: primaryView: all: name: "all" views: - all: name: "all" - list: columns: - "status" - "weather" - "jobName" - "lastSuccess" - "lastFailure" - "lastDuration" - "buildButton" includeRegex: ".*" name: "test_view" Jenkins version: 2.150.3 configuration-as-code-plugin: version: 1.14 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198871.1555696084000.23429.1557490860107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57405) Stop/Disconnect on Idle Timeout feature not working after updating Node description template
Title: Message Title Stefan Verhoeff created an issue Jenkins / JENKINS-57405 Stop/Disconnect on Idle Timeout feature not working after updating Node description template Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-05-10 12:01 Environment: Jenkins ver. 2.150.1, EC2 plugin 1.43 Priority: Minor Reporter: Stefan Verhoeff Observed after upgrade from EC2 plugin 1.42 to 1.43. When changing the "Description" of an EC2 node template in the Jenkins config, the "Stop/Disconnect on Idle Timeout" feature does not work anymore for any nodes created before the change. The nodes stay stopped and new nodes are created instead of the old ones re-used. This also happens for any nodes that were created on Jenkins with an EC2 plugin version <1.43. Because in 1.43 the node names are updated with more information to the instance name (PR-334 [1]). This exception happens with that affect nodes, may be related: May 10, 2019 9:55:53 AM hudson.model.AbstractCIBase updateComputer WARNING: Error updating node EC2 (Mobility RD EU-West-1) - android-m52xlarge-eu-west-1 (i-009cd08cab2a1f2b2), continuing java.lang.NullPointerException at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(EC2RetentionStrategy.java:140) at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:92) at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:50) at hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) at hudson.model.Queue._withLock(Queue.java:1381) at hudson.model.Queue.withLock(Queue.java:1258)
[JIRA] (JENKINS-57404) Jenkins Pipeline: exception when running post action
Title: Message Title
Andreas Zeiler updated an issue
Jenkins / JENKINS-57404
Jenkins Pipeline: exception when running post action
Change By:
Andreas Zeiler
Hello,since Apr. 15th we get an exception when Jenkins is building our Pipeline Job. Our "post" Pipeline looks like this: {code:java}post { always { recordIssues filters: [excludeFile('.*\\/DIR0\\/.*|.*\\/DIR1\\/.*|.*\\/DIR2\\/.*')], tools: [doxygen(pattern: 'doxygen-warnings.log')]publishHTML([allowMissing: false, alwaysLinkToLastBuild: false, keepAll: true, reportDir: 'Documentation/html', reportFiles: 'index.html', reportName: 'Firmware Documentation', reportTitles: '']) } success { script {/* Notify Bitbucket */ notifyBitbucket('SUCCESS') } } failure { script { /* Notify Bitbucket */ notifyBitbucket('FAILED') } }cleanup { echo 'Done! Cleaning Workspace...' cleanWs() }{code} The Pipeline Job builds our Doxygen Documentation. In "post" we check the doxygen.log and publish the html file generated by doxygen. The following exception occurs:{code:java} Error when executing always post condition: java.lang.NullPointerException at org.jenkinsci.plugins.structs.SymbolLookup.findDescriptor(SymbolLookup.java:147) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor477.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:158) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:156) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:160) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:130) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:48) at
[JIRA] (JENKINS-57404) Jenkins Pipeline: exception when running post action
Title: Message Title
Andreas Zeiler created an issue
Jenkins / JENKINS-57404
Jenkins Pipeline: exception when running post action
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-05-10 11:51
Environment:
Ubuntu 18.04 LTS Server Jenkins ver. 2.164.2
Priority:
Minor
Reporter:
Andreas Zeiler
Hello, since Apr. 15th we get an exception when Jenkins is building our Pipeline Job. Our "post" Pipeline looks like this:
post {
always {
recordIssues filters: [excludeFile('.*\\/DIR0\\/.*|.*\\/DIR1\\/.*|.*\\/DIR2\\/.*')], tools: [doxygen(pattern: 'doxygen-warnings.log')]
publishHTML([allowMissing: false,
alwaysLinkToLastBuild: false,
keepAll: true,
reportDir: 'Documentation/html',
reportFiles: 'index.html',
reportName: 'Firmware Documentation',
reportTitles: ''])
} success {
script {
/* Notify Bitbucket */
notifyBitbucket('SUCCESS')
}
} failure {
script {
/* Notify Bitbucket */
notifyBitbucket('FAILED')
}
}
cleanup {
echo 'Done! Cleaning Workspace...'
cleanWs()
}
The Pipeline Job builds our Doxygen Documentation. In "post" we check the doxygen.log and publish the html file generated by doxygen. The following exception occurs:
[JIRA] (JENKINS-57404) Jenkins Pipeline: exception when running post action
Title: Message Title Andreas Zeiler updated an issue Jenkins / JENKINS-57404 Jenkins Pipeline: exception when running post action Change By: Andreas Zeiler Environment: Ubuntu 18.04 LTS Server Ubuntu 16.04 LTS as slave Jenkins ver. 2.164.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199188.1557489065000.23418.1557489420054%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56909) Allow to unlock/lock keychain on demand
Title: Message Title Kazuhide Takahashi assigned an issue to Kazuhide Takahashi Jenkins / JENKINS-56909 Allow to unlock/lock keychain on demand Change By: Kazuhide Takahashi Assignee: Kazuhide Takahashi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198582.155446542.23416.1557489120181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57397) Jenkins Build fails with “java.lang.NullPointerException”
Title: Message Title Mark Waite commented on JENKINS-57397 Re: Jenkins Build fails with “java.lang.NullPointerException” There aren't enough instructions for me to duplicate the problem and the null pointer exception stack trace is not included. Please check the Jenkins log and other locations to see if you can find the full stack trace. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199180.1557480564000.23411.1557488940239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57397) Jenkins Build fails with “java.lang.NullPointerException”
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-57397 Jenkins Build fails with “java.lang.NullPointerException” Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199180.1557480564000.23413.1557488940266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57403) Use natural order to sort Details table
Title: Message Title sunblack created an issue Jenkins / JENKINS-57403 Use natural order to sort Details table Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-05-10 11:19 Priority: Minor Reporter: sunblack If you sort by "File" in "Details" -> "Source Control" I'm getting currently following result: my_file.cpp:109 my_file.cpp:120 my_file.cpp:125 my_file.cpp:26 my_file.cpp:27 my_file.cpp:109 my_file.cpp:363 Expected order: my_file.cpp:26 my_file.cpp:27 my_file.cpp:109 my_file.cpp:120 my_file.cpp:125 my_file.cpp:109 my_file.cpp:363 Add Comment
[JIRA] (JENKINS-57402) Let diagrams interact with Details table
Title: Message Title sunblack created an issue Jenkins / JENKINS-57402 Let diagrams interact with Details table Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-05-10 11:16 Priority: Minor Reporter: sunblack In case you want to see what have changed, compared to reference build, you are doing currently following steps: Go to warnings page Deselect "Outstanding", so only "New" and "Fixes" showed Click within the diagram on "New" => new page (middle click to open new tab doesn't work) Go back to previous page Deselect again "Outstanding" Click within the diagram on "Fixed" => new page It would be much easier if behavior would be changed, so "Details" table get synchronized with the diagram. So if you deselect "Outstanding", you only see "New" and "Fixed" issues in table => no reload of page necessary
[JIRA] (JENKINS-57401) Show path for files
Title: Message Title sunblack created an issue Jenkins / JENKINS-57401 Show path for files Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-05-10 11:03 Priority: Minor Reporter: sunblack Currently you have the choice in Details: Show warnings by Folders, Files, ... Mostly I show into Files. But currently you have always to know, where the file is located in your source tree. So it would be nice if the plugin show path if you hover over the file name or show path behind the name (e.g. `my_file.cpp (/path/without/filename)`) Add Comment
[JIRA] (JENKINS-53259) Jenkins Pipeline build fails when trying to jenkins docker plugin
Title: Message Title
Chris Maes commented on JENKINS-53259
Re: Jenkins Pipeline build fails when trying to jenkins docker plugin
I am trying to run the docker process on another server (not on Jenkins master); something like this:
node('master') {
withDockerServer([uri: 'tcp://docker-server:4243']) {
withDockerContainer([image: 'alpine']) {
sh "pwd"
}
}
}
this fails with the exact same error. Inspired by https://github.com/jenkinsci/docker/issues/626#issuecomment-358331311 I have to use this workaround:
add docker-server as a jenkins slave
mount the /home directory of my jenkins user inside the docker. My Jenkinsfile now looks like this:
node('docker-server') {
withDockerContainer([image: 'alpine', args: '-v /home/jenkins/:/home/jenkins']) {
sh "pwd; ls /usr/local/bin"
}
}
it is just sad that I need to add the docker-server as a node...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jonas Lindström edited a comment on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines [~mkozell] was on to something: the bug is not just in the durable-task-plugin, although the symptoms come from there. It is introduced when you upgrade workflow-job. I have managed to pinpoint it down to a specific version.The following setup does not trigger the bug (relevant plugins listed) . All are at latest version at the time of writing, except workflow-job: * durable-task 1.29 * workflow-api 2.33 * workflow-durable-task-step 2.30 * workflow-step-api 2.19 * workflow-support 3.3 * *workflow-job 2.25*Upgrading workflow-job to 2.27 or later triggers the bug. (2.26 does not exist.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.23353.1557485280463%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57400) Add option to filter warnings
Title: Message Title sunblack created an issue Jenkins / JENKINS-57400 Add option to filter warnings Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-05-10 10:43 Priority: Minor Reporter: sunblack Currently I'm trying to integrate clang-tidy in our build server. But currently it is not really usable, because (run-)clang-tidy just has a `-header-filter` option, which filters header files, but not source files. So moc & qrc files of Qt are generating still error messages. So it would be nice, if this plugin has an option to filter files by relative path (relative to be independent to slave path) via a regex. Add Comment
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jonas Lindström commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines Mike Kozell was on to something: the bug is not just in the durable-task-plugin, although the symptoms come from there. It is introduced when you upgrade workflow-job. I have managed to pinpoint it down to a specific version. The following setup does not trigger the bug. All are at latest version at the time of writing, except workflow-job: durable-task 1.29 workflow-api 2.33 workflow-durable-task-step 2.30 workflow-step-api 2.19 workflow-support 3.3 workflow-job 2.25 Upgrading workflow-job to 2.27 or later triggers the bug. (2.26 does not exist.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.23301.1557485101097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jonas Lindström updated an issue Jenkins / JENKINS-55308 intermittent "terminated" messages using sh in Pipelines Change By: Jonas Lindström Component/s: workflow-job-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.23327.1557485101473%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title
Satoshi Goto updated an issue
Jenkins / JENKINS-56854
ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Change By:
Satoshi Goto
h3. Problem Abstractenv GIT_COMMIT is not always same the real git revision in particular situation.Before pipeline stage begin, two merge commits generated by plugins.It is the reason why the revision doesn't match GIT_COMMIT. GIT_COMMIT, SHA of the current, is defined by [Git Plugin|https://wiki.jenkins.io/display/JENKINS/Git+Plugin].h3. Problem DetailI use [GitHub Branch Source Plugin|https://plugins.jenkins.io/github-branch-source] to run Pull Request job with Jenkinsfile.My job use Jenkinsfile in my github repository.I found GIT_COMMIT is sometime different from real git revision in the stage of Pipeline. When the problem happen, Jenkisn build logs says it causes git merge twice.First merge is to read Jenkinsfile from git, second merge is to setup working directory.So I print the revision in my Pipeline script.env.GIT_COMMIT = 75ddc1933fd10b87c529536e3107ea7313debaea HEAD revision = a98b709283bd47d251dfcc9360b91ffc024af16bGIT_COMMIT is the revision at first merge, and HEAD is the revision at second merge.h3. How to reproduce this problemI test with minimum condition which can reproduce the problem by using it↓[https://github.com/mtgto/jenkins-pipeline-test/blob/prtest/Jenkinsfile][https://github.com/mtgto/jenkins-pipeline-test/pull/1] The problem is only happened below all conditions matched: # The job is Multibranch job. # The job uses pipeline with Jenkinsfile in git repository. # The pull request can't merge fast-forward. # Two merge commits is away at least one second.1, 2: The condition to generate twice merge commits.3: Fast-forward merge doesn't change the revision by time.4: First commit is created at fetching Jenkinsfile. Second commit is created at fetching whole target repository. Git object contains time, it is changed by the second. Same time merge commits always have same revisions.h4. EnvironmentsI use Jenkins 2.164.1 in Docker container to reproduce this problem.{noformat}$ docker run -d --name jenkins -p 8080:8080 --name jenkins -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts-alpine{noformat}I install two plugins while first setup: * [GitHub Branch Source|https://plugins.jenkins.io/github-branch-source] * [Pipeline|https://plugins.jenkins.io/workflow-aggregator]h5. Installed Plugins * Apache HttpComponents Client 4.x API Plugin - 4.5.5-3.0 * Authentication Tokens API Plugin - 1.3 * bouncycastle API Plugin - 2.17 * Branch API Plugin - 2.2.0 * Command Agent Launcher Plugin - 1.3 * Credentials Binding Plugin - 1.18 * Credentials Plugin - 2.1.18 * Display URL API - 2.3.1 * Docker Commons Plugin - 1.13 * Docker Pipeline - 1.17 * Durable Task Plugin - 1.29 * Folders Plugin - 6.7 * Git client plugin - 2.7.6 * Git plugin - 3.9.3 * GIT server Plugin - 1.7 * GitHub API Plugin - 1.95 * GitHub Branch Source Plugin - 2.4.5 * GitHub plugin - 1.29.4 * Jackson 2 API Plugin - 2.9.8 *
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title Satoshi Goto commented on JENKINS-56854 Re: ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub Thanks Liam Newman. My explanation is very sad, sorry. In fact, I came out ahead this problem by not using GIT_COMMIT. I abandon GIT_COMMIT because I DO want to test the revision which pull request merged. I run Jenkins by using Git Plugin in debug mode, so I figure out older GIT_COMMIT is set. But I don't find which plugin is wrong... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198514.155421873.23292.1557484740195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Ronny Borchert commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I got this too today. And reverted only in plugins folder the github-branch-source.bak. But now the plugin manager does not show up the new version, strange. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.23283.1557484200784%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56909) Allow to unlock/lock keychain on demand
Title: Message Title Kazuhide Takahashi commented on JENKINS-56909 Re: Allow to unlock/lock keychain on demand Mathieu Delrocq This is another proposal. Separated the steps to unlock the keychain as per your suggestion. And fixed the problem that the keychain password is saved in plain text. https://github.com/jenkinsci/xcode-plugin/pull/102 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198582.155446542.23270.1557483360099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48295) Cannot load a pipeline shared library from Bitbucket PR with cloudbees-bitbucket-branch-source 2.2.7
Title: Message Title Taras Kostyuk updated an issue Jenkins / JENKINS-48295 Cannot load a pipeline shared library from Bitbucket PR with cloudbees-bitbucket-branch-source 2.2.7 Change By: Taras Kostyuk Attachment: Screen Shot 2019-05-10 at 12.44.53.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186884.1511973444000.23259.1557481560296%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48295) Cannot load a pipeline shared library from Bitbucket PR with cloudbees-bitbucket-branch-source 2.2.7
Title: Message Title Taras Kostyuk closed an issue as Fixed the shared library was't properly configured Jenkins / JENKINS-48295 Cannot load a pipeline shared library from Bitbucket PR with cloudbees-bitbucket-branch-source 2.2.7 Change By: Taras Kostyuk Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186884.1511973444000.23265.1557481680258%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57399) Predefined parameters not passing correct
Title: Message Title thulsi doss krishnan created an issue Jenkins / JENKINS-57399 Predefined parameters not passing correct Issue Type: Bug Assignee: Unassigned Attachments: Untitled.png, Untitled1.png Components: parameterized-trigger-plugin Created: 2019-05-10 09:54 Priority: Minor Reporter: thulsi doss krishnan This is more of a repeat issue JENKINS-15749. Still i have the issue in the jobs that i created . Here in the upstream job i set the predefined parameter as API_BUILD_NUMBER=$BUILD_TIMESTAMP and in the down stream job i cant access the variable value using a windows batch command echo %API_BUILD_NUMBER%. Add Comment
[JIRA] (JENKINS-48295) Cannot load a pipeline shared library from Bitbucket PR with cloudbees-bitbucket-branch-source 2.2.7
Title: Message Title Taras Kostyuk commented on JENKINS-48295 Re: Cannot load a pipeline shared library from Bitbucket PR with cloudbees-bitbucket-branch-source 2.2.7 The following configuration in Mange Jenkins ->Configure system fixed the issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186884.1511973444000.23261.1557481560319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57398) Jenkins Build disappears in jenkins UI but is present in master machine?
Title: Message Title Adharsh M created an issue Jenkins / JENKINS-57398 Jenkins Build disappears in jenkins UI but is present in master machine? Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage-plugin, metrics-diskusage-plugin Created: 2019-05-10 09:33 Priority: Major Reporter: Adharsh M Jenkins builds suddenly disappears from the jenkins UI for certain Jobs. The Job triggers and it can been seen in the ui but suddenly vanishes. The build is present in the master machine. Has anyone faced this before. If so your insights will be really helpful!!! Previously we also saw some of our build history(old builds) being missing when checked in the master all the builds were still present but there was a problem with symlinks being broken in the builds folder for a job lastFailedbuild, Lastsatblebuild were reset to -1 even though there were some failed builds present. But this got resolved once a few plugins(disk usage and metrics-diskusage) that were disabled were re-enabled and a reload configuration were done. Add Comment
[JIRA] (JENKINS-57397) Jenkins Build fails with “java.lang.NullPointerException”
Title: Message Title Adharsh M created an issue Jenkins / JENKINS-57397 Jenkins Build fails with “java.lang.NullPointerException” Issue Type: Bug Assignee: Adharsh M Components: git-plugin, pipeline Created: 2019-05-10 09:29 Priority: Minor Reporter: Adharsh M We have integrated Jenkins with Github to build jobs as and when PR is raised with the github pull request builder plugin. From yesterday when the job gets triggered we are seeing this failure "java.lang.NullPointerException" even before the pipeline starts to execute and the job reports the status to github as failed. Also in the console there is a log that mentions "Resuming build after jenkins restart" but there was no restart at the time when this job was triggered But in a little while the job starts executing and then passed the build again in jenkins? This happens often if we retrigger the job but not always!!! Any idea on why this is happening Jenkins Console: Resuming build at Thu May 09 16:30:11 UTC 2019 after Jenkins restart [Pipeline] End of Pipeline Setting status of b9d1bd39cfae59d607b1a8060f2a8ae2fc180a1e to FAILURE with url https://JENKINS_URL/job/JOB_NAME/103/ and message: 'Build finished. ' java.lang.NullPointerException Finished: FAILURE
[JIRA] (JENKINS-57397) Jenkins Build fails with “java.lang.NullPointerException”
Title: Message Title Adharsh M assigned an issue to Mark Waite Jenkins / JENKINS-57397 Jenkins Build fails with “java.lang.NullPointerException” Change By: Adharsh M Assignee: Adharsh M Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199180.1557480564000.23253.1557480600187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53259) Jenkins Pipeline build fails when trying to jenkins docker plugin
Title: Message Title Chris Maes commented on JENKINS-53259 Re: Jenkins Pipeline build fails when trying to jenkins docker plugin I also have this problem with: jenkins 2.150.3 docker plugin 1.1.6 docker pipeline 1.17 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193334.1535391573000.23250.1557480060436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title vikash srivastava commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks yes its active ,see some bug fixes going in , we use it for our CI pipeline in validation stage. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189195.1521053055000.23213.1557479100436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Brandon Le Sann commented on JENKINS-57371 Re: error message when building PR I had the exact same issue as Niklas Claesson . Closing and reopening the PR did not work. Creating new different PRs still produced the same error (although with different hash values). Ignoring this error message and merging the PR solved the issue and doesn't seem to appear again... Hope it helps. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.23241.1557479340231%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57396) Pods Terminate before container image can download
Title: Message Title Daniel Watrous created an issue Jenkins / JENKINS-57396 Pods Terminate before container image can download Issue Type: Bug Assignee: Guillermo Sanchez Urien Components: kubernetes-ci-plugin Created: 2019-05-10 09:07 Environment: Jenkins 1.164.2, Kubernetes 1.14 Labels: jenkins kuberenetes-plugin Priority: Major Reporter: Daniel Watrous I have a build that uses 9 containers, but the Pod never gets to start because it can't finish downloading in the amount of time (100 seconds) that the kubernetes plugin allows. io.fabric8.kubernetes.client.KubernetesClientTimeoutException: Timed out waiting for [10] milliseconds for [Pod] with name:[api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191] in namespace [jenkins]. at org.csanchez.jenkins.plugins.kubernetes.AllContainersRunningPodWatcher.await(AllContainersRunningPodWatcher.java:134) at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:128) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Adrian Constantin edited a comment on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks Dose anybody have an idea know if the Lockable Resource plugin is still active? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189195.1521053055000.23188.1557478380613%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Adrian Constantin commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks Dose anybody have an idea if the Lockable Resource plugin is still active? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189195.1521053055000.23163.1557478080415%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57395) Create administrative monitor to warn users about Oracle JDK Installer concerns
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57395 Create administrative monitor to warn users about Oracle JDK Installer concerns Issue Type: Improvement Assignee: Devin Nusbaum Components: jdk-tool-plugin Created: 2019-05-10 08:34 Labels: java11 Priority: Minor Reporter: Oleg Nenashev Follow-up to JENKINS-57394. Usage of Oracle JDK implies licensing concerns, and we should likely have a administrative monitor with Warning/Disclaimer. Add Comment
[JIRA] (JENKINS-57394) Rename JDK Tool Plugin to Oracle JDK Installer plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57394 Rename JDK Tool Plugin to Oracle JDK Installer plugin Issue Type: Improvement Assignee: Devin Nusbaum Components: jdk-tool-plugin Created: 2019-05-10 08:32 Labels: java11 Priority: Minor Reporter: Oleg Nenashev The JDK Tool plugin does not really offer a JDK Tool, it comes from the core. The plugin only offers a Oracle JDK installer, which implies a lot of concerns including licensing. We should rename the plugin and update the documentation to make it explicit Add Comment
