[JIRA] (JENKINS-62157) GitHub Enterprise rate limiting no longer working
Title: Message Title Brian Farrell commented on JENKINS-62157 Re: GitHub Enterprise rate limiting no longer working Thanks- I created https://github.com/github-api/github-api/issues/802 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.206080.1588601416000.22241.1588717920125%40Atlassian.JIRA.
[JIRA] (JENKINS-62157) GitHub Enterprise rate limiting no longer working
Title: Message Title
Brian Farrell created an issue
Jenkins / JENKINS-62157
GitHub Enterprise rate limiting no longer working
Issue Type:
Bug
Assignee:
Unassigned
Components:
github-branch-source-plugin
Created:
2020-05-04 14:10
Environment:
github-branch-source v2.6.0
Priority:
Major
Reporter:
Brian Farrell
The changes in JENKINS-59039 have broken rate limiting on our GitHub Enterprise instance. This GHE instance does not return rate limit information via the /rate_limit endpoint
{
"message": "Rate limiting is not enabled.",
"documentation_url": "https://developer.github.com/enterprise/2.19/v3/rate_limit/#get-your-current-rate-limit-status"
}
but does return X-RateLimit headers on every request:
< X-RateLimit-Limit: 5000
< X-RateLimit-Reset: 1588603124
< X-RateLimit-Remaining: 4999
Before JENKINS-59039, it looks like the code called org.kohsuke.github.GitHub#rateLimit, which will return header-based rate limit info if it exists. Now the code calls org.kohsuke.github.GitHub#getRateLimit, which exclusively uses the /rate_limit endpoint. The end result is that the plugin does not throttle itself during organization/repository scanning and for repositories with large
[JIRA] (JENKINS-32393) PATH and HOME are being overwritten when executing command
Title: Message Title Daniel Hursh commented on JENKINS-32393 Re: PATH and HOME are being overwritten when executing command I'm hitting this as well. Our images install various tools and define env variables that they need. Things like JAVA_HOME, JRE_HOME, M2_HOME, ANT_HOME & GRADLE_HOME are all getting clobbered with the values from the docker host. In addition PATH is getting clobbered. We really need a way to blacklist and / or whitelist variables that are to be passed into the container. Several of the environment variables set on the host don't make sense for the images we use to build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.167503.145253315.7628.1580248860840%40Atlassian.JIRA.
[JIRA] (JENKINS-50365) reload pipeline script without executing the job
Title: Message Title Geoff Alexander edited a comment on JENKINS-50365 Re: reload pipeline script without executing the job I also wonder how this is fixed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.189416.152180187.3067.1578339720609%40Atlassian.JIRA.
[JIRA] (JENKINS-50365) reload pipeline script without executing the job
Title: Message Title Geoff Alexander commented on JENKINS-50365 Re: reload pipeline script without executing the job I wonder how this is fixed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.189416.152180187.3065.1578339720566%40Atlassian.JIRA.
[JIRA] (JENKINS-59825) Can't update git client plugin
Title: Message Title Robert Hill resolved as Fixed Solution is posted to "Description" section Jenkins / JENKINS-59825 Can't update git client plugin Change By: Robert Hill Status: Open Resolved Assignee: Robert Hill Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-59825) Can't update git client plugin
Title: Message Title Robert Hill updated an issue Jenkins / JENKINS-59825 Can't update git client plugin Change By: Robert Hill I'm new to Jenkins. I installed the various git plugins and had it working for a pipeline project. Recently, Jenkins notified me of a security vulnerability for the git client. I choose to downgrade from 3.0 to the previous version. After doing that, my pipeline lost it's reference to the git login. Any new pipelines doesn't list git as a choice. When I go into the manage plugins, it doesn't list the git-client with an available update. How do I get it back to using the 3.x version? I found the solution. I went to [https://updates.jenkins-ci.org/download/plugins/] and downloaded .hpi files for git plugin 3.12.1 & git-client 2.8.6. I used the "Advanced" tab within the "Managed Plugins" page and used the update plugins section to install these versions. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you
[JIRA] (JENKINS-59825) Can't update git client plugin
Title: Message Title Robert Hill updated an issue Jenkins / JENKINS-59825 Can't update git client plugin Change By: Robert Hill I'm new to Jenkins. I installed the various git plugins and had it working for a pipeline project. Recently, Jenkins notified me of a security vulnerability for the git client. I choose to downgrade from 3.0 to the previous version. After doing that, my pipeline lost it's reference to the git login. Any new pipelines doesn't list git as a choice. When I go into the manage plugins, it doesn't list the git-client with an available update. How do I get it back to using the 3.x version? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Ward Hopeman commented on JENKINS-58643 Re: CPS Mismatches on cpsScript.InvokeMethod We are also seeing this on Jenkins v2.190.1; Artifactory plugin v3.40; Groovy plugin v2.2 artifactoryUploadexpected to call org.jfrog.hudson.pipeline.common.types.ArtifactoryServer.upload but wound up catching artifactoryUpload; see: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.200910.1563983113000.9877.1571331901142%40Atlassian.JIRA.
[JIRA] (JENKINS-59825) Can't update git client plugin
Title: Message Title Robert Hill created an issue Jenkins / JENKINS-59825 Can't update git client plugin Issue Type: Bug Assignee: Unassigned Components: git-client-plugin Created: 2019-10-17 14:34 Environment: Ubuntu Priority: Major Reporter: Robert Hill I'm new to Jenkins. I installed the various git plugins and had it working for a pipeline project. Recently, Jenkins notified me of a security vulnerability for the git client. I choose to downgrade from 3.0 to the previous version. After doing that, my pipeline lost it's reference to the git login. When I go into the manage plugins, it doesn't list the git-client with an available update. How do I get it back to using the 3.x version? Add Comment
[JIRA] (JENKINS-58818) `Parameterized Remote Trigger Plugin` parameter with equal sign in value gets dropped
Title: Message Title Raj Desai created an issue Jenkins / JENKINS-58818 `Parameterized Remote Trigger Plugin` parameter with equal sign in value gets dropped Issue Type: Bug Assignee: KaiHsiang Chang Attachments: image-2019-08-05-11-15-16-293.png Components: parameterized-remote-trigger-plugin Created: 2019-08-05 18:18 Environment: Jenkins ver. 2.164.2 Parameterized Remote Trigger Plugin - 3.0.8 Labels: plugin pipeline Priority: Major Reporter: Raj Desai The parameter shows the correct value 'cGFzc3dvcmQ=' in the console output but in the remote Jenkins job it gets set to 'cGFzc3dvcmQ'. Console output: First time build. Skipping changelog. > git config core.sparsecheckout # timeout=10 > git checkout -f e432212deecb3cda7108083c492fa828b916d91a Parameterized Remote Trigger Configuration: job: PasswordTest remoteJenkinsName: ug-devops-jenkins parameters: [Password=cGFzc3dvcmQ=] blockBuildUntilComplete: true
[JIRA] (JENKINS-52750) dir step creates a @tmp directory at level.
Title: Message Title Philip Garrett commented on JENKINS-52750 Re: dir step creates a @tmp directory at level. The behavior is both undocumented (as far as I can tell), and surprising, since normally "change current directory" would not be a mutating operation. Also, using the name of the directory requested by the user compounds the confusion, because it's easy to miss the @tmp suffix, or think it's an artifact of the exception rendering. I didn't really notice the @tmp suffix until after I had been fighting with this problem for a while, believing Jenkins was trying to create a directory that already existed. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56980) Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Title: Message Title
Joseph Kesselman updated an issue
Jenkins / JENKINS-56980
Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Change By:
Joseph Kesselman
This spring, we had a job scheduled to trigger at 2AM ("0 2 * * *") fail to execute the morning of the EST/DST switch-over. Our suspicion is that the skip from 01:59 to 03:00 provoked this problem. (Which might also mean that jobs scheduled in that window would run twice the night of the autumn switch-over.)A trivial workaround would to schedule for 01:59 (or, for paranoia's sake, 01:58). But standard scheduler logic Really Should Not be vulnerable to this.Admittedly we're still running Jenkins 2.89.2 (our own fault; we haven't found time to resolve some compatability issues with newer releases), so this may have been fixed Long Ago. Apologies if so. "Better to speak up and risk being thought a fool, than to remain silent and remove all doubt."
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56980) Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Title: Message Title
Joseph Kesselman updated an issue
Jenkins / JENKINS-56980
Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Change By:
Joseph Kesselman
Environment:
This spring, we had a job scheduled to trigger at 2AM ("0 2 * * *") fail to execute the morning of the EST/DST switch-over. Our suspicion is that the skip from 01:59 to 03:00 provoked this problem. (Which might also mean that jobs scheduled in that window would run twice the night of the autumn switch-over.)A trivial workaround would to schedule for 01:59 (or, for paranoia's sake, 01:58). But standard scheduler logic Really Should Not be vulnerable to this.Admittedly we're still running Jenkins 2.89.2 (our own fault; we haven't found time to resolve some compatability issues with newer releases), so this may have been fixed Long Ago. Apologies if so. "Better to speak up and risk being thought a fool, than to remain silent and remove all doubt."
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56980) Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Title: Message Title
Joseph Kesselman created an issue
Jenkins / JENKINS-56980
Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-04-11 15:51
Environment:
This spring, we had a job scheduled to trigger at 2AM ("0 2 * * *") fail to execute the morning of the EST/DST switch-over. Our suspicion is that the skip from 01:59 to 03:00 provoked this problem. (Which might also mean that jobs scheduled in that window would run twice the night of the autumn switch-over.) A trivial workaround would to schedule for 01:59 (or, for paranoia's sake, 01:58). But standard scheduler logic Really Should Not be vulnerable to this. Admittedly we're still running Jenkins 2.89.2 (our own fault; we haven't found time to resolve some compatability issues with newer releases), so this may have been fixed Long Ago. Apologies if so. "Better to speak up and risk being thought a fool, than to remain silent and remove all doubt."
Priority:
Minor
Reporter:
Joseph Kesselman
Add Comment
[JIRA] (JENKINS-56399) Performance plugin not filtering trend data
Title: Message Title Sungjin Yook commented on JENKINS-56399 Re: Performance plugin not filtering trend data Still waiting on the update. Any update will be appreciated. Thank you. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56399) Performance plugin not filtering trend data
Title: Message Title Sungjin Yook edited a comment on JENKINS-56399 Re: Performance plugin not filtering trend data Having same issue that Trend Data filtering not working. Could you take a look into this issue? Trying to adopt this in our production env, and the work is currently blocking our deployment. Appreciate 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56399) Performance plugin not filtering trend data
Title: Message Title Sungjin Yook updated an issue Jenkins / JENKINS-56399 Performance plugin not filtering trend data Change By: Sungjin Yook Priority: Minor Major 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56399) Performance plugin not filtering trend data
Title: Message Title Sungjin Yook commented on JENKINS-56399 Re: Performance plugin not filtering trend data Having same issue that Trend Data filtering not working. Could you take a look into this issue? Appreciate 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55710) Sidebar-Link plugin file upload blocked by CSRF protection
Title: Message Title Bradley Herrin created an issue Jenkins / JENKINS-55710 Sidebar-Link plugin file upload blocked by CSRF protection Issue Type: Bug Assignee: Unassigned Components: sidebar-link-plugin Created: 2019-01-21 16:40 Environment: Ubuntu 18 Kubernetes 1.11 Jenkins version 2.150.1 sidebar-link-plugin 1.10 Chrome Version 71.0.3578.98 (Official Build) (64-bit) Labels: plugin csrf Priority: Minor Reporter: Bradley Herrin When on the /configure page when trying to upload a new image to /userContent using the sidebar-link plugin the following error is generated. HTTP ERROR 403 Problem accessing /plugin/sidebar-link/upload. Reason: No valid crumb was included in the request Powered by Jetty:// 9.4.z-SNAPSHOT The result of this error is due to CSRF protection in Jenkins 2.x. The current workaround is for a user to complete the following steps: Visit /configureSecurity page Disable Prevent Cross Site Request Forgery exploits ** temporarily Visit /configure upload the image desired
[JIRA] (JENKINS-54282) Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk'
Title: Message Title Peter Toennies commented on JENKINS-54282 Re: Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk' Does anyone monitor posts on this forum? Will this issue be fixed in an upcoming Jenkins version? Did I do something wrong on my system when upgrading Jenkins to cause this issue? Thank you, Peter 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54282) Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk'
Title: Message Title Peter Toennies commented on JENKINS-54282 Re: Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk' Does anyone else have this problem? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54282) Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk'
Title: Message Title
Peter Toennies edited a comment on JENKINS-54282
Re: Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk'
Perhaps the behavior I am seeing is related to https://issues.jenkins-ci.org/browse/JENKINS-52008 ("Please wait while Jenkins is starting" page looks bad in 2.128"): >> The page also does not reload automatically when Jenkins starts.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54282) Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk'
Title: Message Title
Peter Toennies commented on JENKINS-54282
Re: Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk'
Perhaps the behavior I am seeing is related to https://issues.jenkins-ci.org/browse/JENKINS-52008 ("Please wait while Jenkins is starting" page looks bad in 2.128"): The page also does not reload automatically when Jenkins starts.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54282) Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk'
Title: Message Title Peter Toennies created an issue Jenkins / JENKINS-54282 Jenkins stuck on 'Please wait while Jenkins is getting ready to work' after pressing 'Reload Configuration from Disk' Issue Type: Bug Assignee: Unassigned Attachments: Jenkins_Reload_Configuration_from_Disk_jenkins_2.130.png Components: jenkins-flowdock Created: 2018-10-26 19:35 Environment: Linux 3.10.0-693.el7.ppc64 java version "1.8.0_171" Java(TM) SE Runtime Environment (build 8.0.5.16 - pxp6480sr5fp16-20180524_01(SR5 FP16)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux ppc64-64-Bit Compressed References 20180523_387150 (JIT enabled, AOT enabled) OpenJ9 - c81abfb OMR - f3f8112 IBM - 4f87eeb) JCL - 20180515_01 based on Oracle jdk8u171-b11 Labels: regression Priority: Minor Reporter: Peter Toennies After upgrading from Jenkins 2.125 to 2.130, the option to do "Reload Configuration from Disk" appears to hang. The screen shows the message in the screenshot indefinitely. After giving up waiting for the screen to come back to the dashboard, I can press refresh on the browser and the Jenkins dashboard does appear. However, I didn't have to do this previously with older Jenkins versions. I tested older versions starting with 2.89.4 and going to versions 2.107.3, 2.121.3, and 2.125 and none of these had the problem. The Jenkins dashboard would appear after a few seconds showing all the
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Also, I can probably try to use the Jenkins version that was the last to use JNA 4.2.1. I think that is jenkins-2.135-1.1.noarch.rpm. I would like to at least go to Jenkins version 2.125 which fixes this issue: "Do not remove workspaces for projects with builds in progress. (issue 27329)". However, I was hoping to use a stable version. The first stable version at 2.125 or higher is 2.138 which is the one I originally tried to use that has JNA 4.5.2 and is missing the libjnidispatch.so that I need. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I was about to open a ticket at https://github.com/java-native-access/jna/issues/new, but the template comments in bug said to go to https://groups.google.com/forum/#!forum/jna-users first. I went there and started a discussion with subject "The libjnidispatch.so file is missing for Linux ppc64 from JNA 4.5.2 which is used with Jenkins 2.138+" 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I looked at jna 4.2.1, 4.5.2, and 5.0.0 from https://github.com/java-native-access/jna/releases. In each tar.gz file I found a lib/native/linux-ppc64.jar file. When I unjarred these from each one, the jna 4.2.1 version contained a libjnidispatch.so. However, the others contained a file named "OUT_OF_DATE" with contents "This file is out of date and needs to be rebuilt". I wonder what that means. I wonder if that means that this version is no longer supported or that there build process is broken. I guess I will try to post something on the github link to try to figure out what is going on. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Was the ppc64 support removed in the more recent JNA versions intentionally or was this an oversight? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Oh, the one from JNA 4.2.1 worked fine for me. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies edited a comment on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I did not have the above problem when install installing Jenkins 2.135.1-1 from https://pkg.jenkins.io/redhat -stable /. I can see from https://jenkins.io/changelog/ that in Jenkins 2.136 the following: Update JNA from 4.2.1 to 4.5.2 to add support for s390x, update GNU C minimal requirement to 2.7 on Unix platforms. (issue 52771) Apparently, the JNA 4.5.2 version added support for some things but removed support for other things. Can the JNA version included with Jenkins add back the Linux ppc64 support for libjnidispatch.so? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I did not have the above problem when install Jenkins 2.135.1-1 from https://pkg.jenkins.io/redhat-stable/. I can see from https://jenkins.io/changelog/ that in Jenkins 2.136 the following: Update JNA from 4.2.1 to 4.5.2 to add support for s390x, update GNU C minimal requirement to 2.7 on Unix platforms. (issue 52771) Apparently, the JNA 4.5.2 version added support for some things but removed support for other things. Can the JNA version included with Jenkins add back the Linux ppc64 support for libjnidispatch.so? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Hi, Craig. I am not sure what you are asking me. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I opened https://issues.jenkins-ci.org/browse/JENKINS-54196 for the problem I found today related to this. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies created an issue Jenkins / JENKINS-54196 Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-22 21:44 Environment: # uname -a Linux localhost 3.10.0-693.el7.ppc64 #1 SMP Thu Jul 6 20:01:28 EDT 2017 ppc64 ppc64 ppc64 GNU/Linux java -version java version "1.8.0_171" Java(TM) SE Runtime Environment (build 8.0.5.16 - pxp6480sr5fp16-20180524_01(SR5 FP16)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux ppc64-64-Bit Compressed References 20180523_387150 (JIT enabled, AOT enabled) OpenJ9 - c81abfb OMR - f3f8112 IBM - 4f87eeb) JCL - 20180515_01 based on Oracle jdk8u171-b11 Labels: jenkins Priority: Major Reporter: Peter Toennies rpm -q jenkins jenkins-2.138.2-1.1.noarch Today I tried upgrade from jenkins-2.89.4-1.1 to jenkins 2.138.2-1.1 on a RHEL7 ppc64 machine. I am getting a java.lang.UnsatisfiedLinkError for 'Native library (com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path'. The complete output is: Unit jenkins.service has begun starting up. Oct 22 12:57:10 runuser[20830]: pam_unix(runuser:session): session opened for user root by (uid=0) Oct 22 12:57:12 jenkins[20825]: Starting Jenkins Exception in
[JIRA] (JENKINS-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies updated JENKINS-15792 Jenkins / JENKINS-15792 jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Change By: Peter Toennies Status: In Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies updated JENKINS-15792 Jenkins / JENKINS-15792 jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Change By: Peter Toennies Status: Resolved In 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I compared the jenkins.war file between jenkins-2.89.4-1.1 and jenkins 2.138.2-1.1 and found these differences affecting the above. The 2.89 jenkins.war file contains jna-4.2.1.jar and the 2.138 jenkins.war file contains jna-4.5.2.jar. I unjarred both of these and found that the 2.89 jna-4.2.1.jar file has these these libjnidispatch.so files: ./com/sun/jna/linux-x86/libjnidispatch.so ./com/sun/jna/linux-x86-64/libjnidispatch.so ./com/sun/jna/linux-arm/libjnidispatch.so ./com/sun/jna/linux-aarch64/libjnidispatch.so ./com/sun/jna/linux-ppc64/libjnidispatch.so ./com/sun/jna/linux-ppc64le/libjnidispatch.so ./com/sun/jna/linux-sparcv9/libjnidispatch.so ./com/sun/jna/sunos-x86/libjnidispatch.so ./com/sun/jna/sunos-x86-64/libjnidispatch.so ./com/sun/jna/sunos-sparc/libjnidispatch.so ./com/sun/jna/sunos-sparcv9/libjnidispatch.so ./com/sun/jna/freebsd-x86/libjnidispatch.so ./com/sun/jna/freebsd-x86-64/libjnidispatch.so ./com/sun/jna/openbsd-x86/libjnidispatch.so ./com/sun/jna/openbsd-x86-64/libjnidispatch.so and then jna-4.5.2 jar file has these: ./com/sun/jna/linux-x86/libjnidispatch.so ./com/sun/jna/linux-x86-64/libjnidispatch.so ./com/sun/jna/linux-arm/libjnidispatch.so ./com/sun/jna/linux-armel/libjnidispatch.so ./com/sun/jna/linux-aarch64/libjnidispatch.so ./com/sun/jna/linux-ppc/libjnidispatch.so ./com/sun/jna/linux-ppc64le/libjnidispatch.so ./com/sun/jna/linux-mips64el/libjnidispatch.so ./com/sun/jna/linux-s390x/libjnidispatch.so ./com/sun/jna/sunos-x86/libjnidispatch.so ./com/sun/jna/sunos-x86-64/libjnidispatch.so ./com/sun/jna/sunos-sparc/libjnidispatch.so ./com/sun/jna/sunos-sparcv9/libjnidispatch.so ./com/sun/jna/freebsd-x86/libjnidispatch.so ./com/sun/jna/freebsd-x86-64/libjnidispatch.so ./com/sun/jna/openbsd-x86/libjnidispatch.so ./com/sun/jna/openbsd-x86-64/libjnidispatch.so It looks like the jna-4.5.2.jar file is not including these: ./com/sun/jna/linux-ppc64/libjnidispatch.so ./com/sun/jna/linux-sparcv9/libjnidispatch.so And added these: ./com/sun/jna/linux-armel/libjnidispatch.so ./com/sun/jna/linux-ppc/libjnidispatch.so ./com/sun/jna/linux-mips64el/libjnidispatch.so ./com/sun/jna/linux-s390x/libjnidispatch.so I think I really need ./com/sun/jna/linux-ppc64/libjnidispatch.so in order for Jenkins to work on our ppc64 machines. Can this be added back? Is there a workaround? Add Comment
[JIRA] (JENKINS-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Since this ticket was already resolved fixed, should I open a new one to report the problem? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15792) jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-15792 Re: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Today I tried upgrade from jenkins-2.89.4-1.1 to jenkins 2.138.2-1.1 on a RHEL7 ppc64 machine. I am getting a java.lang.UnsatisfiedLinkError for 'Native library (com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path'. The complete output is: – Unit jenkins.service has begun starting up. Oct 22 12:57:10 runuser[20830]: pam_unix(runuser:session): session opened for user root by (uid=0) Oct 22 12:57:12 jenkins[20825]: Starting Jenkins Exception in thread "main" java.lang.reflect.InvocationTargetException Oct 22 12:57:12 jenkins[20825]: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Oct 22 12:57:12 jenkins[20825]: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) Oct 22 12:57:12 jenkins[20825]: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) Oct 22 12:57:12 jenkins[20825]: at java.lang.reflect.Method.invoke(Method.java:508) Oct 22 12:57:12 jenkins[20825]: at Main._main(Main.java:227) Oct 22 12:57:12 jenkins[20825]: at Main.main(Main.java:160) Oct 22 12:57:12 jenkins[20825]: Caused by: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path (file:/tmp/jna7389605851826903872jar, file:/tmp/akuma9008425977486382467jar) Oct 22 12:57:12 jenkins[20825]: at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:962) Oct 22 12:57:12 jenkins[20825]: at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:922) Oct 22 12:57:12 jenkins[20825]: at com.sun.jna.Native.(Native.java:190) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.CLibrary.(CLibrary.java:89) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:128) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:116) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.Daemon.daemonize(Daemon.java:106) Oct 22 12:57:12 jenkins[20825]: at com.sun.akuma.Daemon.all(Daemon.java:88) Oct 22 12:57:12 jenkins[20825]: ... 6 more Oct 22 12:57:12 runuser[20830]: pam_unix(runuser:session): session closed for user root Oct 22 12:57:12 jenkins[20825]: [FAILED] Oct 22 12:57:12 systemd[1]: jenkins.service: control process exited, code=exited status=1 Oct 22 12:57:12 systemd[1]: Failed to start LSB: Jenkins Automation Server. – Subject: Unit jenkins.service has failed – Defined-By: systemd – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel – -- Unit jenkins.service has failed. – -- The result is failed. Jenkins starts up fine with 2.89.4-1.1, but not with the most recent stable version of 2.138.2-1.1. Is this a regression? Does anyone have suggestions on how to get Jenkins to start? Do I need to download something additional? Also, I tried to search for libjnidispatch.so on my system with Jenkins 2.89 but could not find it. Where should this file be at? Thank you, Peter
[JIRA] (JENKINS-52803) IBM Application Security on Cloud plugin does not currently allow for third party code to be scanned
Title: Message Title Robert Catalano commented on JENKINS-52803 Re: IBM Application Security on Cloud plugin does not currently allow for third party code to be scanned Hey, just wondering if any progress has been made on this? I'm happy to assist in solving this issue with the plugin if need be. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27413) Handle file parameters
Title: Message Title Chris Snyder commented on JENKINS-27413 Re: Handle file parameters Took a while to find out that this was an issue. Plus one for getting this fixed in an upcoming release. UnstashParam worked for me. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51529) Use a single jenkinsfile across multiple git repos for pull requests?
Title: Message Title carl eastman created an issue Jenkins / JENKINS-51529 Use a single jenkinsfile across multiple git repos for pull requests? Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2018-05-24 17:59 Priority: Minor Reporter: carl eastman We have a single jenkins file that we use for building and deploying across 50 different git repos. With blueocean how can we do the same thing for pull requests? Instead of having to keep 50 copies of the same jenkinsfile in sync across 50 git repos. Add Comment
[JIRA] (JENKINS-50040) This Jenkins appears to have crashed", generating nullPointerException
Title: Message Title Meghali Dhoble commented on JENKINS-50040 Re: This Jenkins appears to have crashed", generating nullPointerException Hi Oleg Nenashev, I recently completed the upgrade activity on my jenkins server and got it upgraded to latest LTS version 2.107.2. With this now I don't see any trace OR crash-dump on the server. Thanks for helping me resolve this. -Meghali Dhoble Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Joe Fowler commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Oleg Nenashev, yes, we should be able to try a patch once you have one available. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Joe Fowler created an issue Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Issue Type: Bug Assignee: Kohei Hasegawa Components: ci-skip-plugin Created: 2018-04-06 01:50 Environment: Ubuntu 16.04 Jenkins 2.107.1 ci-skip plugin 0.0.2 Priority: Major Reporter: Joe Fowler ci-skip setting on jobs can't be set. Setting it, and hitting 'Save' or Apply causes a UnsupportedOperatonException with the following stack trace Stack trace java.lang.UnsupportedOperationException: Refusing to marshal org.jruby.RubyNil for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at org.jenkinsci.jruby.JRubyXStreamConverter.marshal(JRubyXStreamConverter.java:76) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at org.jenkinsci.jruby.JRubyXStreamConverter.marshal(JRubyXStreamConverter.java:76) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at
[JIRA] (JENKINS-50596) Average time display
Title: Message Title carl eastman created an issue Jenkins / JENKINS-50596 Average time display Issue Type: New Feature Assignee: Unassigned Attachments: Screen Shot 2018-04-05 at 9.52.16 AM.png Components: blueocean-plugin Created: 2018-04-05 14:54 Priority: Minor Reporter: carl eastman Something that would be nice to see in the run display view would be the previous average time per stage, similar to the classic job view. Add Comment
[JIRA] (JENKINS-50040) This Jenkins appears to have crashed", generating nullPointerException
Title: Message Title Meghali Dhoble commented on JENKINS-50040 Re: This Jenkins appears to have crashed", generating nullPointerException Thanks Oleg Nenashev, for the quick reply. I am in process of upgrading my Jenkins server, to check if that helps. I will update this ticket after upgrade with my observations. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50040) This Jenkins appears to have crashed", generating nullPointerException
Title: Message Title Meghali Dhoble created an issue Jenkins / JENKINS-50040 This Jenkins appears to have crashed", generating nullPointerException Issue Type: Bug Assignee: Unassigned Attachments: Manage_jenkins_page.PNG Components: core Created: 2018-03-09 12:53 Labels: jenkins Priority: Minor Reporter: Meghali Dhoble On the manage jenkins page getting a message saying "jenkins is crashed" and with a set of warnings followed by it. Manage Jenkins New version of Jenkins (2.110) is available for download This Jenkins appears to have crashed. Warnings have been published for the following currently installed components: On further debugging found below logs, with a trace talking about NullPointerException Feb 27, 2018 1:44:42 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /configure. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:72) at hudson.Functions.filterDescriptors(Functions.java:1863) at sun.reflect.GeneratedMethodAccessor2971.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at
[JIRA] (JENKINS-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title Joe Fowler commented on JENKINS-43062 Re: SSH Host Key Verifiers are not configured for all SSH slaves I just sit 'Save', on each of the nodes without changing anything and the message went away... Still, an aggravation. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42405) Lots of remote channel errors with pipelines and Windows slaves
Title: Message Title Joe Fowler commented on JENKINS-42405 Re: Lots of remote channel errors with pipelines and Windows slaves Thanks Ivan I downgraded that plugin form 2.10 to 2.8, and it has fixed the problem in my case as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42588) Could not fetch branches from source [some-guid] java.lang.NullPointerException
Title: Message Title Craig Muchinsky commented on JENKINS-42588 Re: Could not fetch branches from source [some-guid] java.lang.NullPointerException So to work around the issue I had to manually downgrade branch-api to 2.0.7 by uploading http://updates.jenkins-ci.org/download/plugins/branch-api/2.0.7/branch-api.hpi, and then downgrade cloudbees-folder to 5.18. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42588) Could not fetch branches from source [some-guid] java.lang.NullPointerException
Title: Message Title Craig Muchinsky edited a comment on JENKINS-42588 Re: Could not fetch branches from source [some-guid] java.lang.NullPointerException I suspect this is related to # - JENKINS-42511 -Any thoughts [~stephenconnolly]? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42588) Could not fetch branches from source [some-guid] java.lang.NullPointerException
Title: Message Title Craig Muchinsky commented on JENKINS-42588 Re: Could not fetch branches from source [some-guid] java.lang.NullPointerException I suspect this is related to JENKINS-42511 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42588) Could not fetch branches from source [some-guid] java.lang.NullPointerException
Title: Message Title Craig Muchinsky updated an issue Jenkins / JENKINS-42588 Could not fetch branches from source [some-guid] java.lang.NullPointerException Change By: Craig Muchinsky Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42588) Could not fetch branches from source [some-guid] java.lang.NullPointerException
Title: Message Title Craig Muchinsky commented on JENKINS-42588 Re: Could not fetch branches from source [some-guid] java.lang.NullPointerException Has anybody identified a workaround for this issue? Downgrading the plugin didn't seem to work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Joe Fowler commented on JENKINS-42428 Re: Jenkins master throwing java.io.IOException when running pipeline in swarm client This is actually quite ugly when trying to sort through the logs. Is there a way to filter and ignore these messages? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Joe Fowler commented on JENKINS-42428 Re: Jenkins master throwing java.io.IOException when running pipeline in swarm client This is probably the same as https://issues.jenkins-ci.org/browse/JENKINS-42405 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42405) Lots of remote channel errors with pipelines and Windows slaves
Title: Message Title Joe Fowler commented on JENKINS-42405 Re: Lots of remote channel errors with pipelines and Windows slaves Thanks to the logging, I have confirmed that my error is the same error that is documented in this issue.. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42405) Lots of remote channel errors with pipelines and Windows slaves
Title: Message Title Joe Fowler commented on JENKINS-42405 Re: Lots of remote channel errors with pipelines and Windows slaves Thanks for the link! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42405) Lots of remote channel errors with pipelines and Windows slaves
Title: Message Title Joe Fowler commented on JENKINS-42405 Re: Lots of remote channel errors with pipelines and Windows slaves I've not figured out how to turn on the additional logging? How did you accomplish this? I am curious it the issue I have is the same, or not. I run running a linux master and agents. My error is very similar. Cannot contact DevelopmentBuild1_whyme: java.io.IOException: Remote call on DevelopmentBuild1_whyme failed. My problem started occurring on 2 different Jenkins masters with different agents, and on different machines. The problem seemed to have coincided with plugin updates. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Joe Fowler edited a comment on JENKINS-42428 Re: Jenkins master throwing java.io.IOException when running pipeline in swarm client Interesting, I am getting a very similar error on my pipeline jobs: Cannot contact SERVER_ABC: java.io.IOException: Remote call on SERVER_ABC failed.I have 2 different Jenkins Masters failing to 2 different agents.As noted, the builds execute fine. It is as though some polling is occurring Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Joe Fowler commented on JENKINS-42428 Re: Jenkins master throwing java.io.IOException when running pipeline in swarm client Interesting, I am getting a very similar error on my pipeline jobs: Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35687) Add explicit support for git lfs
Title: Message Title Ian Tait commented on JENKINS-35687 Re: Add explicit support for git lfs Ah there it is. Thank you for the help! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35687) Add explicit support for git lfs
Title: Message Title Ian Tait commented on JENKINS-35687 Re: Add explicit support for git lfs Mark Waite Is there a way to change the timeout time for the LFS pull? Currently it is set at 10 minutes, but we need it to be longer for the first pull to finish successfully. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41563) Periodic StackOverflowError thrown when pipeline build is requested
Title: Message Title Joe Fowler commented on JENKINS-41563 Re: Periodic StackOverflowError thrown when pipeline build is requested Added another stacktrace of a 3rd variation of the failure Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41563) Periodic StackOverflowError thrown when pipeline build is requested
Title: Message Title Joe Fowler updated an issue Jenkins / JENKINS-41563 Periodic StackOverflowError thrown when pipeline build is requested Change By: Joe Fowler Attachment: Stacktrace_3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41583) job-dsl-plugin is not able to generate paramters is template has empty parameter list.
Title: Message Title James Murphy commented on JENKINS-41583 Re: job-dsl-plugin is not able to generate paramters is template has empty parameter list. Trying to recreate from scratch using scripts that I can send you, but now in the current version of Jenkins it does not let me create a template project with an empty parameters list anymore. i get the error: Error No Parameters are specified for this parameterized build My original template was created way back when I had Jenkins 1.452 installed and then we have upgraded several times since (and recently upgraded the Job DSL Plugin). Doesn't look like I will be able to reproduce this error and is probably not something that needs to be addressed in current version. Thank you for you time looking into this, we can probably close it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41583) job-dsl-plugin is not able to generate paramters is template has empty parameter list.
Title: Message Title James Murphy updated an issue Jenkins / JENKINS-41583 job-dsl-plugin is not able to generate paramters is template has empty parameter list. Change By: James Murphy Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41583) job-dsl-plugin is not able to generate paramters is template has empty parameter list.
Title: Message Title James Murphy created an issue Jenkins / JENKINS-41583 job-dsl-plugin is not able to generate paramters is template has empty parameter list. Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2017/Jan/31 1:25 AM Environment: job-dsl-plugin 1.57 jenkins version 2.32.1 RHEL 7.2 Priority: Minor Reporter: James Murphy After upgrading Jenkins DSL plugin from 1.47 to 1.57, noticed that my jobs parameters list were empty if the templates being used had the "this build is parameterized" but did not have any parameters listed in the template. However, if the template does not have that check box marked, then the DSL plugin is able to process the parameters that are passed in and create the job with all the parameters. This is minor as the workaround is to not have any empty parameters list in the template, but was annoying to try and figure out why my parameters were missing all of a sudden after upgrading the plugin. Thought it would be good to document it somewhere in case others run into the same issue.
[JIRA] (JENKINS-41563) Periodic StackOverflowError thrown when pipeline build is requested
Title: Message Title Joe Fowler created an issue Jenkins / JENKINS-41563 Periodic StackOverflowError thrown when pipeline build is requested Issue Type: Bug Assignee: vjuranek Attachments: Stacktrace_1, Stacktrace_2 Components: groovy-plugin Created: 2017/Jan/30 3:06 PM Environment: Jenkins 2.43 running on s390x Ant Plugin This plugin adds Apache Ant support to Jenkins. 1.4 Uninstall Authentication Tokens API Plugin This plugin provides an API for converting credentials into authentication tokens in Jenkins. 1.3 Uninstall bouncycastle API Plugin Provides an stable API to Bouncy Castle related tasks. Plugins using Bouncy Castle should depend on this plugin and not directly on Bouncy Castle 2.16.0 Uninstall Branch API Plugin This plugin provides an API for multiple branch based projects. 1.11.1 Uninstall build timeout plugin This plugin allows builds to be automatically terminated after the specified amount of time has elapsed. 1.18 Uninstall Build Timestamp Plugin This plugin adds BUILD_TIMESTAMP to Jenkins variables and system properties. 1.0.1 Uninstall Credentials Binding Plugin Allows credentials to be bound to environment variables for use from miscellaneous build steps. 1.10 Uninstall Credentials Plugin This plugin allows you to store credentials in Jenkins. 2.1.10 Uninstall CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.12 Uninstall Display URL API Provides an extension point to define alternate URLs for use in notifications. 0.5 Uninstall Docker build step plugin This plugin allows to add various docker commands to your job as build steps. 1.37 Uninstall Docker Commons Plugin Provides the common shared functionality for various Docker-related plugins. 1.6 Uninstall Docker plugin This plugin integrates Jenkins with Docker 0.16.2 Uninstall Docker Slaves Plugin Uses Docker containers to run Jenkins build agents. 1.0.6 Uninstall Durable Task Plugin Library offering an extension point for processes which can run outside of Jenkins yet be monitored. 1.12 Uninstall Email Extension Plugin This plugin is a replacement for Jenkins's email publisher 2.53 Uninstall External Monitor Job Type Plugin Adds the ability to monitor the result of externally executed jobs. 1.7 Uninstall Folders Plugin This plugin allows users to create "folders" to organize
[JIRA] (JENKINS-7321) Ability to re-run a past job with the same or similar parameters
Title: Message Title Ian Tait commented on JENKINS-7321 Re: Ability to re-run a past job with the same or similar parameters +1 Sebastien Vas I agree, there should be an option to use either the original or the current configuration. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39836) CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves
Title: Message Title Kevin Smith resolved as Fixed After some research I recognized that SSHAuthenticator.Matcher did not define a serialVersionUID and was a Serializable class due to CredentialsMatcher. I added a concrete value for this and now every platform and jdk/jre now works successfully. Jenkins / JENKINS-39836 CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves Change By: Kevin Smith Status: Open Resolved Assignee: Nicolas De Loof Kevin Smith Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39836) CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves
Title: Message Title Kevin Smith updated an issue Jenkins / JENKINS-39836 CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves Change By: Kevin Smith Component/s: ssh-credentials-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40457) java.lang.ArrayStoreException when a image pull secret is defined
Title: Message Title Andrew Gunnerson created an issue Jenkins / JENKINS-40457 java.lang.ArrayStoreException when a image pull secret is defined Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Dec/14 9:58 PM Environment: Kubernetes plugin - 0.10-SNAPSHOT (built from 71c946a207fbfc7fcab2b51a66d80d70b56126d2) Priority: Minor Reporter: Andrew Gunnerson When an image pull secret is defined, the containers can no longer start up due to a java.lang.ArrayStoreException being thrown here: https://github.com/jenkinsci/kubernetes-plugin/blob/71c946a207fbfc7fcab2b51a66d80d70b56126d2/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java#L419 The crash appears to have been introduced in this commit: https://github.com/jenkinsci/kubernetes-plugin/commit/4393e55906c02ac03ea668439ec69c8d07f4f091 Stacktrace: Dec 14, 2016 4:47:02 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Dec 14, 2016 4:47:02 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from pd-docker with 1 executors. Remaining excess workload: 0 Dec 14, 2016 4:47:02 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call SEVERE: Error in provisioning; slave=KubernetesSlave name: dynamic-cuke-20161116-1-58b3c2f8d175, template=org.csanchez.jenkins.plugins.kubernetes.PodTemplate@dd75a2d java.lang.ArrayStoreException at java.util.ArrayList.toArray(ArrayList.java:408) at
[JIRA] (JENKINS-39836) CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves
Title: Message Title
Kevin Smith updated an issue
Jenkins / JENKINS-39836
CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves
Change By:
Kevin Smith
Attempting to clone a git repo at the start of a build on an AIX slave Linux Z, P, and PLE slaves . This exception was triggered: {noformat} ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: git@<>:<>/<>.git: Failed to connect at org.jenkinsci.plugins.gitclient.JGitAPIImpl$5.execute(JGitAPIImpl.java:1342) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:332) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:273) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626) at java.lang.Thread.run(Thread.java:804) at ..remote call to cxp01006(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1433) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:797) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy79.execute(Unknown Source) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1042) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at
[JIRA] (JENKINS-39836) CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves
Title: Message Title Kevin Smith updated an issue Jenkins / JENKINS-39836 CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves Change By: Kevin Smith Environment: AIX *Linux 2. 6. 18-128.el5 # 1 SMP Wed Dec 17 11:45:02 EST 2008 s390x s390x s390x GNU/Linux IBM javajava version "1.7.0"Java ( 6100 TM) SE Runtime Environment (build pxz6470_27 - 05 20131115_04)IBM J9 VM (build 2.7, JRE 1.7.0 Linux s390x - 06 64 Compressed References 20131114_175264 (JIT enabled, AOT enabled)J9VM - 1119 R27_Java727_GA_20131114_0833_B175264JIT - tr.r13.java_20131113_50523GC - R27_Java727_GA_20131114_0833_B175264_CMPRSSJ9CL - 20131114_175264 ) JCL - 20131113_01 based on Oracle 7u45 - b18Linux 3.10.0 - 229.ael7b.ppc64le #1 SMP Fri Jan 30 12:03:50 EST 2015 ppc64le ppc64le ppc64le GNU/Linux - --- IBM java java version "1.7.0"Java(TM) SE Runtime Environment (build pap6470 pxl6470_27sr3fp1 - 20110827_01 20150605_01(SR3 FP1 ) ) IBM J9 VM (build 2. 7, JRE 1.7.0 Linux ppc64le-64 Compressed References 20150407_243189 (JIT enabled, AOT enabled)J9VM - R27_Java727_SR3_20150407_1831_B243189JIT - tr.r13.java_20150406_89182GC - R27_Java727_SR3_20150407_1831_B243189_CMPRSSJ9CL - 20150407_243189)JCL - 20150601_01 based on Oracle 7u79-b14Linux 2. 6 .32-279.el6.ppc64 #1 SMP Wed Jun 13 18:19:27 EDT 2012 ppc64 ppc64 ppc64 GNU/Linux IBM javajava version "1.7.0"Java(TM) SE Runtime Environment (build pxp6470_27-20131115_04)IBM J9 VM (build 2.7 , JRE 1.7.0 AIX Linux ppc64-64 20110810_88604 Compressed References 20131114_175264 (JIT enabled, AOT enabled)J9VM - R26_Java726_GA_20110810_1208_B88592 R27_Java727_GA_20131114_0833_B175264 JIT - r11_20110810_20466 tr.r13.java_20131113_50523 GC - R26_Java726_GA_20110810_1208_B88592 R27_Java727_GA_20131114_0833_B175264_CMPRSS J9CL - 20110810_88604 20131114_175264 )JCL - 20110809_01 20131113_01 based on Oracle 7b147 7u45 - b18 --- - Jenkins ver. 1 2 . 532.3 19 SSH Credentials Plugin 1. 6.1 12 Jenkins GIT client plugin 1 2 . 9. 1 .0 Add Comment
[JIRA] (JENKINS-39836) CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves
Title: Message Title Kevin Smith created an issue Jenkins / JENKINS-39836 CLONE - InvalidClassException for SSHAuthenticator$1 when doing a git clone on an Linux Z series, Linux P series, and Linux P LE series slaves Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: ssh-credentials-plugin Created: 2016/Nov/17 7:03 PM Environment: AIX 6.1 (6100-05-06-1119) java version "1.7.0" Java(TM) SE Runtime Environment (build pap6470-20110827_01) IBM J9 VM (build 2.6, JRE 1.7.0 AIX ppc64-64 20110810_88604 (JIT enabled, AOT enabled) J9VM - R26_Java726_GA_20110810_1208_B88592 JIT - r11_20110810_20466 GC - R26_Java726_GA_20110810_1208_B88592 J9CL - 20110810_88604) JCL - 20110809_01 based on Oracle 7b147 Jenkins ver. 1.532.3 SSH Credentials Plugin 1.6.1 Jenkins GIT client plugin 1.9.1 Priority: Major Reporter: Kevin Smith Attempting to clone a git repo at the start of a build on an AIX slave. This exception was triggered: FATAL: Failed to fetch from ssh://@/.git hudson.plugins.git.GitException: Failed to fetch from ssh://@/.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:623) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:855) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at
[JIRA] (JENKINS-38278) Slave initialization w/Kubernetes Plugin: Unable to start native thread OOM exception
Title: Message Title Andrew Gunnerson commented on JENKINS-38278 Re: Slave initialization w/Kubernetes Plugin: Unable to start native thread OOM exception I've updated to remoting (slave.jar) 2.62 and the issue persists. After further investigation, I'm not so convinced that the issue is occurring on the master. I wrote a simple java program that spawns as many threads as it can and it capped out at about 32000 threads (probably because of the max PID limit). Then, I looked at the Jenkins monitoring plugin page and saw that the maximum number of threads that Jenkins had at the same time is around 200.Is there anything else I can test that would help in fixing this issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38278) Slave initialization w/Kubernetes Plugin: Unable to start native thread OOM exception
Title: Message Title Andrew Gunnerson updated an issue Jenkins / JENKINS-38278 Slave initialization w/Kubernetes Plugin: Unable to start native thread OOM exception Change By: Andrew Gunnerson Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38289) ansiblePlaybook pipeline step does not respect environment
Title: Message Title
Andrew Gunnerson created an issue
Jenkins / JENKINS-38289
ansiblePlaybook pipeline step does not respect environment
Issue Type:
Bug
Assignee:
Jean-Christophe Sirot
Components:
ansible-plugin, pipeline
Created:
2016/Sep/16 9:15 PM
Environment:
Jenkins 2.7.3 Pipeline plugin 2.3 Ansible plugin 0.5
Priority:
Minor
Reporter:
Andrew Gunnerson
The "ansiblePlaybook" step doesn't seem to respect variables set with "env.NAME = VALUE" or with "withEnv([NAME: VALUE]) {...}". In my particular case, ANSIBLE_CONFIG needs to be set so that a custom Ansible configuration file can be used. I've created a simple pipeline job to illustrate the issue (linked below). Despite ANSIBLE_CONFIG being set, it is not present in the ansible-playbook process's environment (confirmed by looking at /proc/ANSIBLE_PID/environ). Pipeline job: https://gist.github.com/agunnerson-ibm/dd065a950269d68fbb84e64425bad08e#file-pipeline-groovy Job log: https://gist.github.com/agunnerson-ibm/dd065a950269d68fbb84e64425bad08e#file-job-log (Note how it loads /etc/ansible/ansible.cfg instead of the custom config)
[JIRA] (JENKINS-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title Kevin Smith closed an issue as Fixed The changes needed for this defect were fixed once I correctly implemented the Cloud API. Jenkins / JENKINS-30203 When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution Change By: Kevin Smith Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title Kevin Smith edited a comment on JENKINS-30203 Re: When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution @ [~ pjdarton , ] Thanks for the update. In fact those changes were done by me as there was no one else looking at them. I've been using them in-house for about 1 year now with excellent success.Regards,Kevin J. Smith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30203) When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remai
Title: Message Title Kevin Smith commented on JENKINS-30203 Re: When there are more jobs assigned to a cloud slave (once provisioned) than the computer can handle, then the cloud should be able to provision a new slave(s) to handle the remaining jobs needing execution @pjdarton, Thanks for the update. In fact those changes were done by me as there was no one else looking at them. I've been using them in-house for about 1 year now with excellent success. Regards, Kevin J. Smith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38278) Slave initialization w/Kubernetes Plugin: Unable to start native thread OOM exception
Title: Message Title Andrew Gunnerson created an issue Jenkins / JENKINS-38278 Slave initialization w/Kubernetes Plugin: Unable to start native thread OOM exception Issue Type: Bug Assignee: Carlos Sanchez Components: core, kubernetes-plugin Created: 2016/Sep/16 2:33 PM Environment: Jenkins 2.7.3 (official docker image jenkins:2.7.3) - Docker host has 16GB of memory and runs nothing else Slave (official docker image jenkinsci/jnlp-slave:latest) - Kubernetes hosts all have 48GB of memory Kubernetes plugin 0.8 Priority: Minor Reporter: Andrew Gunnerson I'm running into an issue where the slaves dynamically spun up by the Kubernetes plugin randomly cause an "unable to create new native thread" exception during the slave.jar connection phase. As far as I can tell, the exception is throws on the Jenkins master, not the slave. Both the master and slave are running in the official docker containers (jenkins:2.7.3 and jenkinsci/jnlp-slave:latest, respectively). The first thing I did was check the process limits from the "jenkins" user inside the Jenkins master container. The limits seem to be much higher than what should be needed for a server that only has 7 jobs (where everything runs on slaves). It usually gets to the point where a build for a job is created, but doesn't actually do anything. The job hangs with either no output or the same OOM exception. I've included the process limits and relevant logs below. Is there anything else I can provide that would help solve the problem? — Jenkins master process limits from inside the container: https://gist.github.com/agunnerson-ibm/dccb6c8c2edc6a498f9c377d96f43481#file-process_limits_master-txt Slave connection log: https://gist.github.com/agunnerson-ibm/dccb6c8c2edc6a498f9c377d96f43481#file-slave-log slave.jar log:
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Matt Hess commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I just tried the work around above by Yury Zaytsev ( explained more in JENKINS-30744)... this works... Thank you!!! However, it would still be nice to have an actual fix and get this out of the jenkinFile. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Matt Hess commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Please fix.. this defect renders Jenkins at my current location as "not the way forward". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches I downloaded and built the plugin from the master stream. After loading the pre-release plugin into Jenkins plugins, seems to be working fine. Thanks Mark. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy edited a comment on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches I downloaded and built the plugin from the master stream branch . After loading the pre-release plugin into Jenkins plugins, seems to be working fine. Thanks Mark. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches Hi Mark, No special reason, it was the previously installed version, and I had known it was working then (plus the downgrade to previously installed version button was conveniently there). Also we were against a deadline, and choose to downgrade instead of going through all the commits searching for messages that had newlines, and that second link you posted to download the build from is no longer pointing to an existing artifact... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34309) git-client-plugin: StringIndexOutOfBoundsException when parsing branches
Title: Message Title James Murphy commented on JENKINS-34309 Re: git-client-plugin: StringIndexOutOfBoundsException when parsing branches Hi, We hit the same issue during one of our builds, wanted to add that we were able to downgrade the git client plugin back to 1.8.1 to bypass the issue. Not sure how to go back and search each commit that happened for a new line in our case the culprit commit is not the most recent, so we would need to go back and update ones that happened several commits ago... not sure how to do that yet Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35087) Old data not upgrading from 1.653 to 1.651.2
Title: Message Title Tammy Parker commented on JENKINS-35087 Re: Old data not upgrading from 1.653 to 1.651.2 It was not solved. The Manage Old Data shows up intermittently after my plugin updates. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35087) Old data not upgrading from 1.653 to 1.651.2
Title: Message Title Tammy Parker edited a comment on JENKINS-35087 Re: Old data not upgrading from 1.653 to 1.651.2 I have the same error starting today when I attempted to update all of my plugins.Also, after the update attempt via 'Download now and install after restart', the plugins are still listed as needing an update; I think the update did not occur as I forgot to check each individual plugin before pushing the 'Download now and install after restart' button... I seem to have resolved my issue by going back to the Update Plugins and properly selecting them and then doing the 'Download now and install after restart'.When I saw they were successfully downloaded, I did a http://jenkins_server_url:8080/safeRestartI no longer have the Manage Old Data issue showing up. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35087) Old data not upgrading from 1.653 to 1.651.2
Title: Message Title Tammy Parker commented on JENKINS-35087 Re: Old data not upgrading from 1.653 to 1.651.2 I have the same error starting today when I attempted to update all of my plugins. Also, after the update attempt via 'Download now and install after restart', the plugins are still listed as needing an update; I think the update did not occur as I forgot to check each individual plugin before pushing the 'Download now and install after restart' button... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-34954) Upgrade from LTS 1.651.1 to 1.651.2 broke functionality of parameterized trigger plugin
Title: Message Title James Murphy commented on JENKINS-34954 Re: Upgrade from LTS 1.651.1 to 1.651.2 broke functionality of parameterized trigger plugin Hi, I think I am hitting the same issue. I am using Jenkins for our Continuous Integration Pipeline and over the weekend the Jenkins Master upgraded itself from 1.651.1 to 1.651.2, and several of our jobs that are using the parameterized trigger plugin are now failing. While I can revert back to 1.651.1, I am wondering what the solution going forward should be? Right now I have a shell script that runs in JobA, it creates a bunch of variables (for example, location to some of the build artifacts stored on an external file server) and pipes them to a file that I later pass to JobB using "Parameters from properties file". This works extremely well for us because we don't necessarily need to create the parameters in JobB before hand, as long as JobA passes them in via the properties file. Since I see there appear to be several people hitting the same issue with the parameterized trigger pluggin after upgrade to 1.651.2 or greater, I am wondering if there will be some fix to revert back the requirement that the job that is being triggered must pre-define/declare the parameters before they can be passed in? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27449) Node description string missing from Configuration Matrix's Node/Label section
Title: Message Title Peter Toennies commented on JENKINS-27449 Re: Node description string missing from Configuration Matrix's Node/Label section Does this problem still occur with the latest 1.x Jenkins versions? If so, are there any plans to fix it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27530) ISE from RunMap.put after reloading configuration from disk
Title: Message Title Jeff Miller commented on JENKINS-27530 Re: ISE from RunMap.put after reloading configuration from disk If "Reload Configuration from disk" isn't going to be fully supported then it should be removed entirely. I've worked around this issue by downloading the code and modifying the java.hudson.model.Job.java class to force it to read from the file "nextBuildNumber" every time it needs nextBuildNumber. However this has the side effect of builds that enter the Pending Build Queue while a reload is occurring, will not show up in the build history until another "Reload configuration from disk" is performed. Some legacy support maybe needed to added back in on the onLoad() method. /* * The MIT License * * Copyright (c) 2004-2009, Sun Microsystems, Inc., Kohsuke Kawaguchi, Martin Eigenbrodt, Matthew R. Harrah, Red Hat, Inc., Stephen Connolly, Tom Huybrechts, CloudBees, Inc. * * Permission is hereby granted, free of charge, to any person obtaining a copy * of this software and associated documentation files (the "Software"), to deal * in the Software without restriction, including without limitation the rights * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell * copies of the Software, and to permit persons to whom the Software is * furnished to do so, subject to the following conditions: * * The above copyright notice and this permission notice shall be included in * all copies or substantial portions of the Software. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN * THE SOFTWARE. */ package hudson.model; import com.google.common.base.Function; import com.google.common.collect.Collections2; import com.infradna.tool.bridge_method_injector.WithBridgeMethods; import hudson.BulkChange; import hudson.EnvVars; import hudson.Extension; import hudson.ExtensionPoint; import hudson.PermalinkList; import hudson.Util; import hudson.cli.declarative.CLIResolver; import hudson.model.Descriptor.FormException; import hudson.model.Fingerprint.Range; import hudson.model.Fingerprint.RangeSet; import hudson.model.PermalinkProjectAction.Permalink; import hudson.model.listeners.ItemListener; import hudson.search.QuickSilver; import hudson.search.SearchIndex; import hudson.search.SearchIndexBuilder; import hudson.search.SearchItem; import hudson.search.SearchItems; import hudson.security.ACL; import hudson.tasks.LogRotator; import hudson.util.AlternativeUiTextProvider; import hudson.util.ChartUtil; import hudson.util.ColorPalette; import hudson.util.CopyOnWriteList; import hudson.util.DataSetBuilder; import hudson.util.DescribableList; import hudson.util.FormApply; import hudson.util.Graph; import hudson.util.ProcessTree; import hudson.util.QuotedStringTokenizer; import hudson.util.RunList; import hudson.util.ShiftedCategoryAxis; import hudson.util.StackedAreaRenderer2; import hudson.util.TextFile; import hudson.widgets.HistoryWidget; import hudson.widgets.HistoryWidget.Adapter; import hudson.widgets.Widget; import jenkins.model.BuildDiscarder; import jenkins.model.DirectlyModifiableTopLevelItemGroup; import jenkins.model.Jenkins; import jenkins.model.ProjectNamingStrategy; import jenkins.security.HexStringConfidentialKey; import jenkins.util.io.OnMaster; import
[JIRA] [core] (JENKINS-27530) ISE from RunMap.put after reloading configuration from disk
Title: Message Title Jeff Miller commented on JENKINS-27530 Re: ISE from RunMap.put after reloading configuration from disk This issue is not related to any plugins, it can be reproduced easily with a freestyle job, and doing a reload. Please see Jenkins 33794. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34079) Python pexpect process wrapped within a python script always timeout on lengthly process when running it via Jenkins (under "Execute Shell")
Title: Message Title Thawngzapum Lian updated an issue Jenkins / JENKINS-34079 Python pexpect process wrapped within a python script always timeout on lengthly process when running it via Jenkins (under "Execute Shell") Change By: Thawngzapum Lian Please note that the aforementioned issue was not found in Version 1.579.The issue surfaced after upgrade to Version 1.653 Python pexpect process wrapped in a python script always timeout on lengthy process when running it via Jenkins (under "Execute Shell"). The same script successfully ran when directly running it on console terminal. Can Jenkins shell can be run under pseudo terminal slave (pts/N)?Python script as run as belowpython python-script.py --param1= --param2=Python pexpect process was instantiated in python-script.pyMonitoring the process (Manual run vs. Jenkins run)Jenkins run (Script did NOT run OK)UID PID PPID C STIME TTY TIME CMDroot 11909 31184 0 21:52 ? 00:00:00 /bin/sh -xe /tmp/hudson2869108017601047728.shManual Run (Script ran OK)root 2356 18925 0 21:00 pts/000:00:01 /bin/sh -xe /tmp/hudson2869108017601047728.sh Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34079) Python pexpect process wrapped within a python script always timeout on lengthly process when running it via Jenkins (under "Execute Shell")
Title: Message Title Thawngzapum Lian created an issue Jenkins / JENKINS-34079 Python pexpect process wrapped within a python script always timeout on lengthly process when running it via Jenkins (under "Execute Shell") Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/07 3:13 AM Environment: Red Hat Enterprise Linux Server release 7.2 (Maipo) Jenkins Version 1.653 The aforementioned issue was not found in Version 1.579 Priority: Major Reporter: Thawngzapum Lian Python pexpect process wrapped in a python script always timeout on lengthy process when running it via Jenkins (under "Execute Shell"). The same script successfully ran when directly running it on console terminal. Can Jenkins shell can be run under pseudo terminal slave (pts/N)? Python script as run as below python python-script.py --param1= --param2= Python pexpect process was instantiated in python-script.py Monitoring the process (Manual run vs. Jenkins run) Jenkins run (Script did NOT run OK) UID PID PPID C STIME TTY TIME CMD root 11909 31184 0 21:52 ? 00:00:00 /bin/sh -xe /tmp/hudson2869108017601047728.sh Manual Run (Script ran OK) root 2356 18925 0 21:00 pts/0 00:00:01
