[JIRA] (JENKINS-13493) GitPlugin should garbage collect
Title: Message Title Stephan Krull commented on JENKINS-13493 Re: GitPlugin should garbage collect @Attendees: Whatever the usual process is with git-plugin related issues: This one should really be replanned. Can you pls take care to get it into a proper review and planning? 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-46419) Hung builds
Title: Message Title Stephan Krull commented on JENKINS-46419 Re: Hung builds Just want to give you notice that I have a hung build again today with version 1.12.1 (on Jenkins 2.121.3 (LTS)). This is stacktrace of the thread: Executor #0 for Atlantis01 : executing T3-widgets-svogt #75 java.util.regex.Pattern$CharProperty.match(Pattern.java:3776) java.util.regex.Pattern$Curly.match0(Pattern.java:4260) java.util.regex.Pattern$Curly.match(Pattern.java:4234) java.util.regex.Pattern$Start.match(Pattern.java:3461) java.util.regex.Matcher.search(Matcher.java:1248) java.util.regex.Matcher.find(Matcher.java:637) org.jenkinsci.plugins.periodicreincarnation.Utils.checkFile(Utils.java:304) org.jenkinsci.plugins.periodicreincarnation.Utils.checkBuild(Utils.java:165) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.periodicTriggerRestart(AfterbuildReincarnation.java:139) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:69) org.jenkinsci.plugins.periodicreincarnation.AfterbuildReincarnation.onCompleted(AfterbuildReincarnation.java:18) hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211) hudson.model.Run.execute(Run.java:1843) hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) hudson.model.ResourceController.execute(ResourceController.java:97) hudson.model.Executor.run(Executor.java:429) @Jochen A. Fürbacher: This looks like it is related to this regex problem we saw before. Can you confirm? 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
[JIRA] (JENKINS-43156) Provide Node and NPM to Path does not work
Title: Message Title Stephan Krull commented on JENKINS-43156 Re: Provide Node and NPM to Path does not work @Nikolas Falco: OK, sorry for missing the note and all these issues. I can understand your frustration. Will try to build your extra branch. 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-43156) Provide Node and NPM to Path does not work
Title: Message Title
Stephan Krull updated an issue
Jenkins / JENKINS-43156
Provide Node and NPM to Path does not work
Change By:
Stephan Krull
I have updated the NodeJS Plugin yesterday from version 0.2.2 to 1.1.3 on our Jenkins instance. Afterwards I upgraded Jenkins from 2.32.1 to 2.32.3.We have several FreeStyle jobs that are building with Node.js with the following configuration: * set up the path with the corresponding Node.js version, using no specific nprmrc file:!Screenshot from 2017-03-28 10-45-41.png! * then have a shell execution build step running some node or npm commands, you could test with{code:java}node -version{code} After restart of Jenkins all of our jobs fail, it seems like the plugin is not able to prepare the build environment correctly. And here is the console output: !image-2017-03-28-11-09-14-187.png!
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"
[JIRA] (JENKINS-43156) Provide Node and NPM to Path does not work
Title: Message Title Stephan Krull updated an issue Jenkins / JENKINS-43156 Provide Node and NPM to Path does not work Change By: Stephan Krull Attachment: image-2017-03-28-11-09-14-187.png 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-43156) Provide Node and NPM to Path does not work
Title: Message Title Stephan Krull created an issue Jenkins / JENKINS-43156 Provide Node and NPM to Path does not work Issue Type: Bug Assignee: Nikolas Falco Attachments: Screenshot from 2017-03-28 10-45-41.png Components: nodejs-plugin Created: 2017/Mar/28 8:50 AM Environment: Jenkins 2.32.3 (LTS) a lot of other plugins NodeJS Plugin 1.1.3 Priority: Critical Reporter: Stephan Krull I have updated the NodeJS Plugin yesterday from version 0.2.2 to 1.1.3 on our Jenkins instance. Afterwards I upgraded Jenkins from 2.32.1 to 2.32.3. We have several FreeStyle jobs that are building with Node.js with the following configuration: set up the path with the corresponding Node.js version, using no specific nprmrc file: then have a shell execution build step running some node or npm commands, you could test with node -version After restart of Jenkins all of our jobs fail, it seems like the plugin is not able to prepare the
[JIRA] (JENKINS-38991) NullPointerException in logging of DependencyCheckExecutor
Title: Message Title Stephan Krull commented on JENKINS-38991 Re: NullPointerException in logging of DependencyCheckExecutor @Steve Springett: Meanwhile our Jenkins server runs with plugin version 1.4.5 and I have not heard of any more problems. This issue should be marked as resolved then. Sorry for the big delay, there were priorities ... 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-35113) Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Title: Message Title Stephan Krull commented on JENKINS-35113 Re: Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin @huybrechts, Kohsuke Kawaguchi: Any news on that one? I think it is important to add a note to the WIKI page, at least. It is more adviseable to fix any outstanding implementations for SECURITY-170 (see here). 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-35522) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title Stephan Krull commented on JENKINS-35522 Re: Upgrade to Credentials 2.1.0+ API for populating credentials drop-down @Stephen Connolly: Could it be that this change lead to problems finding available credentials. This is what I see after adding (another) node to our Jenkins LTS 2.19.4 instance with the latest SSH Slaves plugin version 1.12 installed (and dependent plugin versions: credentials (version:2.1.10), ssh-credentials (version:1.12)): The global credentials (that work with every node that is established) do not show up. Please advise if there is need to create a new issue for that. BTW: the plugin page needs an update since there still is reference to version 1.11 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-35522) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title Stephan Krull updated an issue Jenkins / JENKINS-35522 Upgrade to Credentials 2.1.0+ API for populating credentials drop-down Change By: Stephan Krull 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-38991) NullPointerException in logging of DependencyCheckExecutor
Title: Message Title Stephan Krull reopened an issue @Steve Springett: After installing version 1.4.4 and running the build we still have a failure, see stacktrace 09:24:30 [DependencyCheck] Scanning: /var/lib/jenkins/jobs/AuthServer/workspace/authserver/build/libs/authserver.jar 09:24:31 [DependencyCheck] Analyzing Dependencies 09:26:50 [DependencyCheck] One or more exceptions were thrown while executing Dependency-Check 09:26:50 [DependencyCheck] Exception Caught: java.util.ConcurrentModificationException 09:26:50 ERROR: Build step failed with exception 09:26:50 java.lang.NullPointerException 09:26:50 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.performBuild(DependencyCheckExecutor.java:109) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$1.call(AbstractDependencyCheckBuilder.java:90) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$1.call(AbstractDependencyCheckBuilder.java:87) 09:26:50 at hudson.remoting.LocalChannel.call(LocalChannel.java:45) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder.perform(AbstractDependencyCheckBuilder.java:87) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckBuilder.perform(DependencyCheckBuilder.java:209) 09:26:50 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 09:26:50 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) 09:26:50 at hudson.model.Build$BuildExecution.build(Build.java:205) 09:26:50 at hudson.model.Build$BuildExecution.doRun(Build.java:162) 09:26:50 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 09:26:50 at hudson.model.Run.execute(Run.java:1720) 09:26:50 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 09:26:50 at hudson.model.ResourceController.execute(ResourceController.java:98) 09:26:50 at hudson.model.Executor.run(Executor.java:404) 09:26:50 Build step 'Invoke OWASP Dependency-Check analysis' marked build as failure The NullPointerException still arises from the "for" loop. ec.getExceptions() seems to return null objects. Can you fix this? Jenkins / JENKINS-38991 NullPointerException in logging of DependencyCheckExecutor Change By: Stephan Krull Resolution: Fixed Status: Closed Reopened
[JIRA] (JENKINS-38991) NullPointerException in logging of DependencyCheckExecutor
Title: Message Title Stephan Krull commented on JENKINS-38991 Re: NullPointerException in logging of DependencyCheckExecutor Thank you for the quick fix! Any schedule for the 1.4.4 release? 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-38991) NullPointerException in logging of DependencyCheckExecutor
Title: Message Title Stephan Krull reopened an issue @Steve Springett: Now there won't be any NPE's arrising from that method any more. But there also won't probably arrise any valuable information from exception handlings. I. e. users are not able to interpret errors due to missing information on the exception type that has been thrown. The calls to log(String message) should be checked. In my opinion at least at line 108 is a need for an additional information about the Throwable type that is contained in the ExceptionCollection. Jenkins / JENKINS-38991 NullPointerException in logging of DependencyCheckExecutor Change By: Stephan Krull Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38991) NullPointerException in logging of DependencyCheckExecutor
Title: Message Title Stephan Krull created an issue Jenkins / JENKINS-38991 NullPointerException in logging of DependencyCheckExecutor Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2016/Oct/14 1:22 PM Environment: Jenkins 2.7.4 OWASP Dependency-Check Plugin 1.4.3 Priority: Critical Reporter: Stephan Krull We are currently seeing the following stacktrace on failing builds caused by the plugin: 08:54:25 ERROR: Build step failed with exception 08:54:25 java.lang.NullPointerException 08:54:25 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.log(DependencyCheckExecutor.java:376) 08:54:25 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.performBuild(DependencyCheckExecutor.java:108) 08:54:25 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$1.call(AbstractDependencyCheckBuilder.java:90) 08:54:25 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$1.call(AbstractDependencyCheckBuilder.java:87) 08:54:25 at hudson.remoting.LocalChannel.call(LocalChannel.java:45) 08:54:25 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder.perform(AbstractDependencyCheckBuilder.java:87) 08:54:25 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckBuilder.perform(DependencyCheckBuilder.java:209) 08:54:25 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 08:54:25 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) 08:54:25 at hudson.model.Build$BuildExecution.build(Build.java:205) 08:54:25 at
[JIRA] (JENKINS-17212) Git clean broken on Windows
Title: Message Title Stephan Krull commented on JENKINS-17212 Re: Git clean broken on Windows We get the aforementioned exception too. Jenkins 2.7.1 (LTS); Git Plugin (2.5.2); Git Client Plugin (1.19.7) A job running on a Windows node. Build steps create output directories in the Git repository that is referenced by the job. Next run occasionally fails with the exception while JGit tries to clean up. On the Windows node no file handle could by found by Process Explorer. We deactivated "Clean before Checkout" and created a build step before SCM to run "git clean -fdx" (see https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep). 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-37058) change term "switches" to "options"
Title: Message Title Stephan Krull updated an issue Jenkins / JENKINS-37058 change term "switches" to "options" Change By: Stephan Krull The Gradle buildstep provides a string parameter named "Switches". The term is a bit misleading as the value you put in there is actually a Gradle commandline *option*.I would prefer to change the used term "Switches" to "Options" to conform to the standard.To be done: Change parameter name and description (by the way: the description could link to the [Gradle commandline documentation|https://docs . gradle.org/current/userguide/gradle_command_line.html]). 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-37058) change term "switches" to "options"
Title: Message Title Stephan Krull updated an issue Jenkins / JENKINS-37058 change term "switches" to "options" Change By: Stephan Krull The Gradle buildstep provides a string parameter named "Switches". The term is a bit misleading as the value you put in there is actually a Gradle commandline *option*.I would prefer to change the used term "Switches" to "Options" to conform to the standard. To be done: Change parameter name and description. 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-37058) change term "switches" to "options"
Title: Message Title Stephan Krull updated an issue Jenkins / JENKINS-37058 change term "switches" to "options" Change By: Stephan Krull Attachment: Screenshot from 2016-07-29 10-56-09.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-37058) change term "switches" to "options"
Title: Message Title Stephan Krull created an issue Jenkins / JENKINS-37058 change term "switches" to "options" Issue Type: Improvement Assignee: wolfs Components: gradle-plugin Created: 2016/Jul/29 8:59 AM Priority: Minor Reporter: Stephan Krull The Gradle buildstep provides a string parameter named "Switches". The term is a bit misleading as the value you put in there is actually a Gradle commandline option. I would prefer to change the used term "Switches" to "Options" to conform to the standard. Add Comment
[JIRA] (JENKINS-36562) Wrong link to JIRA issues from plugin page
Title: Message Title Stephan Krull commented on JENKINS-36562 Re: Wrong link to JIRA issues from plugin page Seems to be a common problem (see i.e. JENKINS-16997) 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-36562) Wrong link to JIRA issues from plugin page
Title: Message Title Stephan Krull updated an issue Jenkins / JENKINS-36562 Wrong link to JIRA issues from plugin page Change By: Stephan Krull Priority: Critical Major 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-36562) Wrong link to JIRA issues from plugin page
Title: Message Title Stephan Krull created an issue Jenkins / JENKINS-36562 Wrong link to JIRA issues from plugin page Issue Type: Bug Assignee: Thomas Fürer Attachments: imageedit_1_9366240262.gif Components: thinBackup Created: 2016/Jul/11 9:00 AM Priority: Critical Reporter: Stephan Krull The link to the JIRA issues of this plugin is wrong. See https://wiki.jenkins-ci.org/display/JENKINS/thinBackup Link target of the marked (see imageedit_1_9366240262.gif) "Open issues" text leads to http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide=true=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27thinBackup-plugin%27 instead of https://issues.jenkins-ci.org/browse/JENKINS-36311?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20%27thinBackup%27 Add Comment
[JIRA] (JENKINS-24464) Show backup process/progress
Title: Message Title Stephan Krull commented on JENKINS-24464 Re: Show backup process/progress I am voting for this issue with an alternate solution to show process in the build queue: You could probably add additional banner text to the Jenkins default shutdown information banner. 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.
