[JIRA] (JENKINS-40421) Too many levels of symbolic links/Archiving artifact stuck
Title: Message Title Audrey Azra commented on JENKINS-40421 Re: Too many levels of symbolic links/Archiving artifact stuck https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9f3f99bc2a792fee1c160e0/core/src/main/java/hudson/tasks/ArtifactArchiver.java#L251 perhaps tuning system property value hudson.FilePath.VALIDATE_ANT_FILE_MASK_BOUND? Any recommendations or other suggestions Daniel? 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-40421) Too many levels of symbolic links/Archiving artifact stuck
Title: Message Title Audrey Azra created an issue Jenkins / JENKINS-40421 Too many levels of symbolic links/Archiving artifact stuck Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/13 9:00 PM Environment: core 1.642.3 Labels: core archiving artifacts Priority: Major Reporter: Audrey Azra When we have the symbolic links in src code like, dir1 -> . dir2 -> ../../../.. Symptoms observed during this problematic phase: The “Archiving artifact” step under Post- build phase get stuck. We can see the never ending cycling icon… the slave node will report error like “too many levels of symbolic links” and ping response time would gradually degrade, eventually killing the slave. the build log may also have error like WARN: Caught error while checking for symbolic links
[JIRA] (JENKINS-36030) WARNING: Process leaked file descriptors
Title: Message Title Audrey Azra commented on JENKINS-36030 Re: WARNING: Process leaked file descriptors We are seeing similar issue on our slaves: Jenkins ver. 1.642.2, Git client 1.19.5 Any insight on how to resolve/workaround this issue?? Jul 25, 2016 8:29:57 AM hudson.Proc$LocalProc join WARNING: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information java.lang.Exception at hudson.Proc$LocalProc.join(Proc.java:329) at hudson.Proc.joinWithTimeout(Proc.java:168) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1706) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1454) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314) 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:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34722) Unbounded searches with BuildUtil.getDownstreamBuild
Title: Message Title Audrey Azra commented on JENKINS-34722 Re: Unbounded searches with BuildUtil.getDownstreamBuild Steven Christou: Any news or workaround on 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-36361) javax.servlet.ServletException in pluginmanager
Title: Message Title Audrey Azra commented on JENKINS-36361 Re: javax.servlet.ServletException in pluginmanager We encounted same issue : Core 1.596.3 - subversion plugin 1.54. Upgrading subversion plugin to 2.6 workaround resolved 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] [core] (JENKINS-16585) Node configuratin save button takes to Error 500 page always
Audrey Azra commented on JENKINS-16585 Node configuratin save button takes to Error 500 page always In our case, this happens after renaming a slave while using LTS 1.480.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Audrey Azra assigned JENKINS-14362 to Audrey Azra 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Change By: Audrey Azra (03/Feb/14 3:37 PM) Assignee: JesseGlick AudreyAzra This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-20511) hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
Audrey Azra commented on JENKINS-20511 hudson.maven.MavenBuild MissingFieldException: No field targetType found in class hudson.plugins.jobConfigHistory.JobConfigBadgeAction We also see this bug on Jenkins LTS 1.509.4 ; We don't have buildtriggerbadge installed This appears post upgrade from jobconfighistory 2.4 to 2.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-20511) hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
Audrey Azra edited a comment on JENKINS-20511 hudson.maven.MavenBuild MissingFieldException: No field targetType found in class hudson.plugins.jobConfigHistory.JobConfigBadgeAction We also see this bug on Jenkins LTS 1.509.4 ; We don't have buildtriggerbadge installed This appears post upgrade from jobconfighistory 2.4 to 2.5 Both Freestyle Maven job types affected This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra commented on JENKINS-15309 NPE (isEmpty) from main.groovy What about authenticated? Do you have the JOB: DISCOVER permission set there? If so, try removing it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra commented on JENKINS-15309 NPE (isEmpty) from main.groovy I've seen this happen when Anonymous was granted the JOB:discover permission (Project-based Matrix Authorization Strategy) Removing the check-mark resolved it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra edited a comment on JENKINS-15309 NPE (isEmpty) from main.groovy I've seen this happen when Anonymous was granted only the OVERALL: Read JOB:discover permission Selecting both JOB: READ DISCOVER permissions resolved the issue or removing the discover altogether also resolved it. (Project-based Matrix Authorization Strategy) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15309) NPE (isEmpty) from main.groovy
Audrey Azra edited a comment on JENKINS-15309 NPE (isEmpty) from main.groovy I've seen this happen when Anonymous was granted only the OVERALL: Read JOB:discover permission Selecting both JOB: READ DISCOVER permissions resolved the issue or removing the discover altogether also resolved it (but then users get the 404 error when accessing a job from a URL) (Project-based Matrix Authorization Strategy) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Audrey Azra commented on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated We are facing the same problem (Jenkins LTS 1.466.2 Nested View 1.9) Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users; As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Audrey Azra edited a comment on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated We are facing the same problem (Jenkins LTS 1.466.2 Nested View 1.9) using Project-based Matrix Authorization Strategy Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users; As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Audrey Azra edited a comment on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated We are facing the same problem (Jenkins LTS 1.466.2 Nested View 1.9) using Project-based Matrix Authorization Strategy Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users; As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME) Note: This issue was not visible when we were running Jenkins 1.450 / Nested view plugin 1.9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Audrey Azra edited a comment on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated We are facing the same problem (Jenkins LTS 1.466.2 Nested View 1.9) using Project-based Matrix Authorization Strategy Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users; As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME) Note: This issue was not visible when we were running Jenkins 1.450 / Nested view plugin 1.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15065) Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart.
Audrey Azra created JENKINS-15065 Gerrit server suddenly shutdown and as a consequence the Jenkins Gerrit-Trigger fails to restart. Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 06/Sep/12 5:46 PM Description: Manage Jenkins page displays this Error: “The connection to Gerrit is down! Check your settings and the Gerrit server” Issue: When the Gerrit server shuts down suddenly, the Gerrit trigger loses connectivity and stops working. The only way to get it restarted is to restart the whole Jenkins instance. Attempting to restart the gerrit trigger in Jenkins by using the Control box does not work. Firebug POSTs to this: http://jenkins:8210/descriptorByName/com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement/startConnection and never receives a response from the server. Jenkins log files doesn't provide more information. Environment: Jenkins version: 1.450 Jenknins Gerrit-trigger version: 2.5.2 Gerrit version: 2.4.2 Jenkins master server: OS: Linux 2.6.18-194.el5 #1 SMP x86_64 x86_64 x86_64 GNU/Linux Browser: Firefox 15.0 Gerrit server : Linux 2.6.18-194.el5 #1 SMP x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Priority: Minor Reporter: Audrey Azra This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
