[JIRA] (JENKINS-60454) Jenkins.instance is missing after restart
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-60454 Jenkins.instance is missing after restart Change By: GMC Software Development B Corporate Labels: lts-candidate 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.203532.1576121478000.2794.1585572720306%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title GMC Software Development B Corporate commented on JENKINS-60153 Re: NullPointerException in Build failure analyzer Hi! IMHO, this issue was specific/local to build-failure-analyzer itself and is not the cause of the failed-job-deactivator failure; i.e., still a NPE but I assume that there's a completely different stack-trace. At least, the incompatibility of failed-job-deactivator an to the plugin-interface of bfa 1.23 or higher is similar to the already fixed issue https://issues.jenkins.io/browse/JENKINS-59204 (incompatibility of claim / bfa plug-in, after change of bfa plugin-interface). Note (to Eric Boehm): Maybe, a new bug-entry is needed, which refers to this issue as similar cause ?! [And someone has to fix/maintain the failed-job-deactivator] Best regards from Salzburg, Markus 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.203018.1573630888000.2034.1582094580251%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title
GMC Software Development B Corporate commented on JENKINS-60153
Re: NullPointerException in Build failure analyzer
IMHO, this issue was introduced by the commit https://github.com/jenkinsci/build-failure-analyzer-plugin/commit/3f2fa7a021f2a833800fc5c9a4f97b3d9b8d0abf My tests have identified the groovy-script in ...bfa/model/FailureCauseMatrixBuildAction/summary.groovy (ine #35 as already mentioned by the backtrace) as cause: {{def rootFailureDisplayData = my.getFailureCauseDisplayData()}} {{ if (PluginImpl.getInstance().isNoCausesEnabled() || !rootFailureDisplayData.isEmpty()) {}} because my.getFailureCauseDisplayData() calls FailureCauseMatrixBuildAction.getFailureCauseDisplayData(MatrixRun run := null) I will test, whether the patch (as unified diff) summary.groovy.patch will fix this issue Best regards from Salzburg, Markus
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.203018.1573630888000.1542.1580887260271%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-60153 NullPointerException in Build failure analyzer Change By: GMC Software Development B Corporate Attachment: summary.groovy.patch 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.203018.1573630888000.1535.1580887080339%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title GMC Software Development B Corporate commented on JENKINS-60153 Re: NullPointerException in Build failure analyzer Same failure with build-failure-analyzer 1.24.1 and Jenkins LTS version 2.190.3 on Windows Server 2019. org.apache.commons.jelly.JellyTagException: jar:file:/C:/webserver/Jenkins/war/WEB-INF/lib/jenkins-core-2.190.3.jar!/hudson/model/AbstractBuild/index.jelly:110:84: java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) ... and much more (see comment above). IMHO, I've raised the severity from minor to major. 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.203018.1573630888000.9230.1575010620237%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-60153 NullPointerException in Build failure analyzer Change By: GMC Software Development B Corporate Priority: Minor Major 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.203018.1573630888000.9227.1575010560272%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title
GMC Software Development B Corporate edited a comment on JENKINS-59204
Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191
It seems to be a kind of compatibility-missmatch between claim- and bfa-plugin.The claim plugin uses following code (see ClaimBuildFailureAnalyzer.java #44):{quote}{{public static boolean isBFAEnabled() {}} {{ return (Jenkins.getInstance().getPlugin("build-failure-analyzer") != null}}{{ && Jenkins.getInstance().getPlugin(PluginImpl.class).isGlobalEnabled());}}}{quote}With release 1.23.0 of the Build Failure Analyzer the class PluginImpl does no longer extends the interface hudson.Plugin; it was changed to jenkins.model.GlobalConfiguration. I guess, that the core-method getPlugin returns null and therefore, another GlobalConfiguration-compatible implementation has to be used (for this newer bfa-release).
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.201470.1566815964000.3653.1570597920725%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title
GMC Software Development B Corporate edited a comment on JENKINS-59204
Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191
It seems to be a kind of compatibility-missmatch between claim- and bfa-plugin.The claim plugin uses following code (see ClaimBuildFailureAnalyzer.java #44):{quote}{{ public static boolean isBFAEnabled() {}} {{ return (Jenkins.getInstance().getPlugin("build-failure-analyzer") != null}} {{ && Jenkins.getInstance().getPlugin(PluginImpl.class).isGlobalEnabled());}} \{{ } }} {quote}With release 1.23.0 of the Build Failure Analyzer the class PluginImpl does no longer extends the interface hudson.Plugin; it was changed to jenkins.model.GlobalConfiguration. I guess, that the core-method getPlugin returns null and therefore, another GlobalConfiguration-compatible implementation has to be used (for this newer bfa-release).
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.201470.1566815964000.3651.1570597920702%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title
GMC Software Development B Corporate edited a comment on JENKINS-59204
Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191
It seems to be a kind of compatibility-missmatch between claim- and bfa-plugin.The claim plugin checks uses following code (see ClaimBuildFailureAnalyzer.java #44):{quote} {{ public static boolean isBFAEnabled() {}}{{ return (Jenkins.getInstance().getPlugin("build-failure-analyzer") != null}}{{ && Jenkins.getInstance().getPlugin(PluginImpl.class).isGlobalEnabled());}} \ {{ }}}{quote}With release 1.23.0 of the plugin Build Failure Analyzer the class PluginImpl does no longer extends the interface hudson.Plugin , ; it was changed to jenkins.model.GlobalConfiguration. I guess, that the core-method getPlugin returns null and therefore, another GlobalConfiguration-compatible implementation has to be used (for this newer bfa-release).
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.201470.1566815964000.3633.1570597800318%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title
GMC Software Development B Corporate commented on JENKINS-59204
Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191
It seems to be a kind of compatibility-missmatch between claim- and bfa-plugin. The claim plugin checks uses following code (see ClaimBuildFailureAnalyzer.java #44):
public static boolean isBFAEnabled() { return (Jenkins.getInstance().getPlugin("build-failure-analyzer") != null && Jenkins.getInstance().getPlugin(PluginImpl.class).isGlobalEnabled()); {{ }}}
With release 1.23.0 of the plugin Build Failure Analyzer the class PluginImpl does no longer extends the interface hudson.Plugin, it was changed to jenkins.model.GlobalConfiguration. I guess, that the core-method getPlugin returns null and therefore, another GlobalConfiguration-compatible implementation has to be used (for this newer bfa-release).
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.201470.1566815964000.3623.1570597740473%40Atlassian.JIRA.
[JIRA] (JENKINS-58202) File-pattern of report-files no longer configurable
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-58202 File-pattern of report-files no longer configurable Issue Type: Bug Assignee: Nikolas Falco Attachments: screen-xunit.jpg Components: xunit-plugin Created: 2019-06-26 04:51 Environment: Jenkins ver. 2.176.1, Windows server 2019 x64 xUnit-plugin 2.3.5 Priority: Critical Reporter: GMC Software Development B Corporate In "older" freestyle-jobs the file-pattern is still used, but with the current xUnit-release 2.3.5 this parameter is no longer shown nor can be changed. Within the raw XML-config-file of these older jobs the XML-item beginns with and have still have an pattern-entry. See attached sreenshot (screen-xunit.jpg) showing the current presentation of this post-build action ... Best regards from Salzburg, Markus
[JIRA] (JENKINS-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title
GMC Software Development B Corporate edited a comment on JENKINS-51515
Re: Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Hi!The command-line tools tool unzip will show shows warnings (about absolute path spec):{noformat}>unzip -o zip.zipArchive: zip.zipwarning: stripped absolute path spec from /subdir/file2.txt inflating: subdir/file2.txtwarning: stripped absolute path spec from /file1.txt inflating: file1.txt{noformat}
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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title GMC Software Development B Corporate commented on JENKINS-51515 Re: Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active Hi! The command-line tools unzip will show warnings (about absolute path spec): >unzip -o zip.zip Archive: zip.zip warning: stripped absolute path spec from /subdir/file2.txt inflating: subdir/file2.txt warning: stripped absolute path spec from /file1.txt inflating: file1.txt 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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title
GMC Software Development B Corporate edited a comment on JENKINS-51515
Re: Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Thanks for the quick response!Okay, I've attached the (very, very simple) job-configuration file ([^config.xml]), the origin artifacts-file {{[...]/builds/1/[^archive.zip]}} (note: compress-artifacts-plugin used) and the (from UI) downloaded archive [^zip.zip] (which contains the additional root/folder-node '_'.In addition, I've attached a (partial and annotated) screenshot [^screenshot1.png] of the UI - URL: [http://localhost:8080/job/ TestArchiveDownload / 1/artifact/|http://localhost:8080/job// TestArchiveDownload/1/artifact/] , from where I've downloaded the attached file {{zip.zip}}. Best regards from Salzburg, Markus
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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title
GMC Software Development B Corporate edited a comment on JENKINS-51515
Re: Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Thanks for the quick response!Okay, I've attached the (very, very simple) job-configuration file ([^config.xml]), the origin artifacts-file {{[...]/builds/1/[^archive.zip]}} (note: compress-artifacts-plugin used) and the (from UI) downloaded archive [^zip.zip] (which contains the additional root/folder-node '_' ) .In addition, I've attached a (partial and annotated) screenshot [^screenshot1.png] of the UI - URL: [http://localhost:8080/job/TestArchiveDownload/1/artifact/|http://localhost:8080/job//TestArchiveDownload/1/artifact/] , from where I've downloaded the attached file {{zip.zip}}.Best regards from Salzburg, Markus
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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title GMC Software Development B Corporate commented on JENKINS-51515 Re: Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active Thanks for the quick response! Okay, I've attached the (very, very simple) job-configuration file (config.xml), the origin artifacts-file [...]/builds/1/archive.zip (note: compress-artifacts-plugin used) and the (from UI) downloaded archive zip.zip (which contains the additional root/folder-node '_'. In addition, I've attached a (partial and annotated) screenshot screenshot1.png of the UI - URL: http://localhost:8080/job//TestArchiveDownload/1/artifact/ , from where I've downloaded the attached file zip.zip. Best regards from Salzburg, Markus 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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-51515 Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active Change By: GMC Software Development B Corporate Attachment: screenshot1.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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-51515 Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active Change By: GMC Software Development B Corporate Attachment: zip.zip 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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-51515 Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active Change By: GMC Software Development B Corporate Attachment: archive.zip 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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-51515 Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active Change By: GMC Software Development B Corporate Attachment: config.xml 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-51515) Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-51515 Downloaded (zipped) Artifact seems to be corrupt, if compress-artifact is active Issue Type: Bug Assignee: Oliver Gondža Components: compress-artifacts-plugin, core Created: 2018-05-24 05:30 Environment: Jenkins 2.124 on Windows 7 (x64), compress-artifacts 1.10, copyartifact 1.40 Labels: user-experience Priority: Minor Reporter: GMC Software Development B Corporate Hi! I'm testing the current jenkins-version with compress-artifacts and copyartifact 1.40 (which implements ArtifactManager). This new release of the copyartifact-plugin works with this new version of copyartifact, but there's a small issue on the download artifacts UI: If I download the complete build-artifacts (URL: http://localhost:8080/job/Test/lastSuccessfulBuild/artifact/*zip*/.zip) a file with the name "zip.zip" will be downloaded [without compress-artifacts, the name is archive.zip]. This Zip-archive contains an additional root-node/folder '_' an all other files and folders are located under this node. Therefore, the Windows-explorer shows no content after download (within the builtin ZIP-viewer). 7-Zip (for example) seems to interpret this root-node as additional - but unnamed - folder-hierarchy; e.g. If I go into _ -> output of [...]\Downloads\zip.zip this is shown as [...]\Downloads\zip.zip\\output\ Additional notes:
[JIRA] (JENKINS-51000) Method FilePath.copyRecursiveTo() does not fail, if channels on different agents
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-51000 Method FilePath.copyRecursiveTo() does not fail, if channels on different agents Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-04-25 14:44 Environment: Jenkins ver. 2.107.2 on Windows Server 2008 R2 (x64) Priority: Minor Reporter: GMC Software Development B Corporate Hi! I'm using a "small" Groovy-script (with scriptler plugin) to copy files from or to the workspace of different builds, which maybe located on (different) agents. My first approach was to use (at least) the method FilePath.copyRecursiveTo(include_pattern, exclude_pattern, Destination), which is suitable if the destination-channel is equal to source-channel (same node or within master) or one of these channels is null (I.e, on master). But, if files should be copied between different agents, all files are copied to the master (at the given 'raw' path). Okay, I've found a solution for my script by using an temporary TGZ-File on the master as intermediate storage. Looking into the source-code of FilePath.copyRecursiveTo seems to ignore this 'illegal' combination and assumes, that the target is located on the master. Maybe the Core-implementation should detect this 4rd combination (dest-channel != src-channel and booth are not null) as unexpected and throws an exception (like 'unsuitable communication-partners'). Best regards from Salzburg, Markus
[JIRA] (JENKINS-50824) "Excessive" exception logging on writing org.jenkinsci.plugins.resourcedisposer.AsyncResourceDisposer.xm
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-50824 "Excessive" exception logging on writing org.jenkinsci.plugins.resourcedisposer.AsyncResourceDisposer.xm Issue Type: Improvement Assignee: Oliver Gondža Components: resource-disposer-plugin Created: 2018-04-16 13:28 Environment: Jenkins LTS 2.107.1 on Windows Server 2008 R2 x64, ws-cleanup 0.34, resource-disposer 0.8 Labels: exception Priority: Minor Reporter: GMC Software Development B Corporate Hi! In our environment with 4 agents and many concurrent builds (of different jobs), the log contains many entries like: Apr 13, 2018 5:26:09 AM WARNING hudson.util.AtomicFileWriter commit Unable to move atomically, falling back to non-atomic move. java.nio.file.AccessDeniedException: C:\webserver\Jenkins\atomic466027149674640611tmp -> C:\webserver\Jenkins\org.jenkinsci.plugins.resourcedisposer.AsyncResourceDisposer.xml at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsFileCopy.move(WindowsFileCopy.java:301) at sun.nio.fs.WindowsFileSystemProvider.move(WindowsFileSystemProvider.java:287) at java.nio.file.Files.move(Files.java:1395) at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:191) at hudson.XmlFile.write(XmlFile.java:198) at
[JIRA] (JENKINS-50420) Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-50420 Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4 Issue Type: Bug Assignee: Stefan Wolf Components: build-monitor-plugin, groovy-postbuild-plugin Created: 2018-03-27 05:28 Environment: Jenkins LTS 2.107.1 on Windows Server 2008 R2 x64, build-monitor-plugin 1.12+build.201708172343 groovy-postbuild 2.4 badge 1.2 Labels: exception Priority: Blocker Reporter: GMC Software Development B Corporate Hi! After upgrading groovy-postbuild to version 2.4, which does split/extracte badge- and summary-features into the badge-plugin, this "combination" is no longer compatible with the current release of the build-monitor plugin; I.e., shows following exception in log ... Mar 27, 2018 7:10:41 AM WARNING org.kohsuke.stapler.HttpResponseRenderer$Default handleJavaScriptProxyMethodCall call to /$stapler/bound/4edcd493-d025-402e-bfaa-f596f57a8fd0/fetchJobViews failed java.lang.ClassNotFoundException: org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildAction at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(Unknown Source) Caused: java.lang.NoClassDefFoundError: org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildAction at
[JIRA] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title GMC Software Development B Corporate commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Sorry for delayed response ... I've only found one SVNError-related stack-trace within a build-log on the same day; but time differs about 40 minutes (log-entry on master has the timestamp Mar 22, 2018 2:50:34 PM): Note: We are using timestamper-plugin to get/show local time within build-logs. [14:10:55] Checking out a fresh workspace because Jenkins failed to detect the current workspace E:\Jenkins\workspace\GMC_AdHocBuild [14:10:55] ERROR: svn: E155010: The node 'E:\Jenkins\workspace\GMC_AdHocBuild' was not found. [14:10:55] org.tmatesoft.svn.core.SVNException: svn: E155010: The node 'E:\Jenkins\workspace\GMC_AdHocBuild' was not found. [14:10:55] at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70) [14:10:55] at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SvnWcDbConflicts.readConflictInternal(SvnWcDbConflicts.java:365) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SvnWcDbConflicts.readConflict(SvnWcDbConflicts.java:342) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readConflicts(SVNWCDb.java:3395) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.readConflicts(SVNWCDb.java:3355) [14:10:55] at org.tmatesoft.svn.core.internal.wc17.db.SVNWCDb.opReadTreeConflict(SVNWCDb.java:2797) [14:10:55] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetInfo.run(SvnNgGetInfo.java:74) [14:10:55] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgGetInfo.run(SvnNgGetInfo.java:45) [14:10:55] at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) [14:10:55] at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) [14:10:55] at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239) [14:10:55] at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) [14:10:55] at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2497) [14:10:55] at hudson.scm.subversion.UpdateUpdater$TaskImpl.parseSvnInfo(UpdateUpdater.java:126) [14:10:55] at hudson.scm.subversion.UpdateUpdater$TaskImpl.getSvnCommandToUse(UpdateUpdater.java:88) [14:10:55] at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:131) [14:10:55] at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:168) [14:10:55] at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1030) [14:10:55] at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1006) [14:10:55] at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:979) [14:10:55] at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2816) [14:10:55] at hudson.remoting.UserRequest.perform(UserRequest.java:207) [14:10:55] at hudson.remoting.UserRequest.perform(UserRequest.java:53) [14:10:55] at hudson.remoting.Request$2.run(Request.java:358) [14:10:55] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) [14:10:55] at java.util.concurrent.FutureTask.run(Unknown Source) [14:10:55] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [14:10:55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [14:10:55] at hudson.remoting.Engine$1$1.run(Engine.java:98) [14:10:55] at java.lang.Thread.run(Unknown Source) [14:10:55] Cleaning local Directory .
[JIRA] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title
GMC Software Development B Corporate updated an issue
Jenkins / JENKINS-50339
log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Change By:
GMC Software Development B Corporate
Hi!I've found following log-entry, which may is JEP-200 relevant: { { quote} Mar 22, 2018 2:50:34 PM WARNING jenkins.security.ClassFilterImpl lambda$isBlacklisted$1org.tmatesoft.svn.core.SVNErrorMessage in [ file:/C:/xxx/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.9.1.jar |file:///C:/xxx/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.9.1.jar] might be dangerous, so rejecting; see [ https://jenkins.io/redirect/class-filter/ ]{quote } } Note: There are no other JEP-200 or subversion-related log-entries; also svn-checkout (in builds) were successfull.Best regards from Salzburg,Markus
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
[JIRA] (JENKINS-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title
GMC Software Development B Corporate created an issue
Jenkins / JENKINS-50339
log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Issue Type:
Bug
Assignee:
Ivan Fernandez Calvo
Components:
subversion-plugin
Created:
2018-03-22 14:09
Environment:
Jenkins LTS 2.107.1 on Windows Server 2008 R2 x64, and Java(TM) SE Runtime Environment 1.8.0_161-b12 subversion-plugin (newest release) 2.10.4
Labels:
JEP-200
Priority:
Major
Reporter:
GMC Software Development B Corporate
Hi! I've found following log-entry, which may is JEP-200 relevant: {{Mar 22, 2018 2:50:34 PM WARNING jenkins.security.ClassFilterImpl lambda$isBlacklisted$1 org.tmatesoft.svn.core.SVNErrorMessage in file:/C:/xxx/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.9.1.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/}} Note: There are no other JEP-200 or subversion-related log-entries; also svn-checkout (in builds) were successfull. Best regards from Salzburg, Markus
[JIRA] (JENKINS-42460) EnvInject-Permission not shown/maintainable (after restart) correctly
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-42460 EnvInject-Permission not shown/maintainable (after restart) correctly Change By: GMC Software Development B Corporate Hi!Since we have enabled permissions-check for the Environment Injector Plugin (note: the additional option 'Do not show injected variables' is not set), the 'Env. Inject' permission (ViewVars) is not shown/maintainable (in Manage and assign roles) after a restart of our Jenkins-master.[see attached image 'Sample1.png']Additionally, If I would save/apply the configured permissions (in this state), all envinject-related permissions were lost (I.e., all "org.jenkinsci.plugins.envinject.EnvInjectPlugin.ViewVars" permission-entries in config.xml are removed)!As work-around, I have to uncheck and check (and apply afterwards) the 'Enable permissions' (for Environment Injector Plugin) in 'Configure System' to restore the expected 'normal' behavior ( int within time after a restart).Best regards from Salzburg,Markus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42460) EnvInject-Permission not shown/maintainable (after restart) correctly
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-42460 EnvInject-Permission not shown/maintainable (after restart) correctly Change By: GMC Software Development B Corporate Hi!Since we have enabled permissions-check for the Environment Injector Plugin (note: the additional option 'Do not show injected variables' is not set), the 'Env. Inject' permission (ViewVars) is not shown/maintainable (in Manage and assign roles) after a restart of our Jenkins-master.[see attached image 'Sample1.png']Additionally, If I would save/apply the configured permissions (in this state), all envinject-related permissions were lost (I.e., all "org.jenkinsci.plugins.envinject.EnvInjectPlugin.ViewVars" permission-entries in config.xml are removed)!As work-around, I have to uncheck and check (and apply afterwards) the 'Enable permissions' (for Environment Injector Plugin) in 'Configure System' to restore the expected 'normal' behavior ( int time after a restart).Best regards from Salzburg,Markus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42460) EnvInject-Permission not shown/maintainable (after restart) correctly
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-42460 EnvInject-Permission not shown/maintainable (after restart) correctly Issue Type: Bug Assignee: Oleg Nenashev Attachments: Sample1.png Components: envinject-plugin, role-strategy-plugin Created: 2017/Mar/03 9:28 AM Environment: Jenkins 2.47 (on Windows Server 2008 R2 x64), envinject 1.93.1, role-strategy 2.3.2, matrix-auth 1.4 Labels: user-experience Priority: Minor Reporter: GMC Software Development B Corporate Hi! Since we have enabled permissions-check for the Environment Injector Plugin (note: the additional option 'Do not show injected variables' is not set), the 'Env. Inject' permission (ViewVars) is not shown/maintainable (in Manage and assign roles) after a restart of our Jenkins-master. [see attached image 'Sample1.png'] Additionally, If I would save/apply the configured permissions (in this state), all envinject-related permissions were lost (I.e., all "org.jenkinsci.plugins.envinject.EnvInjectPlugin.ViewVars" permission-entries in config.xml are removed)! As work-around, I have to uncheck and check (and apply afterwards) the 'Enable permissions' (for Environment Injector Plugin) in 'Configure System' to restore the expected 'normal' behavior (after a restart). Best regards from Salzburg, Markus
[JIRA] (JENKINS-39497) No recursive expansion in promoted build
Title: Message Title
GMC Software Development B Corporate updated an issue
Jenkins / JENKINS-39497
No recursive expansion in promoted build
Change By:
GMC Software Development B Corporate
We have determined a problem with using an environment-variable, which are defined by using another variable (Ie. recursive expansion) in a promoted build.Following (minimal) scenario:a) Inject environment variable {noformat} Output2=E:\\Temp\\$PROMOTED_NUMBER {noformat} ... and the console shows ...{noformat}[EnvInject] - Injecting environment variables from a build step.[EnvInject] - Injecting as environment variables the properties content Output=E:\Temp\$PROMOTED_NUMBER{noformat}b) Using this variable as Remote File Location in ArtifactDeployer (I.e., $Output) will use "E:\Temp\$PROMOTED_NUMBER" as destination-folder (what was not our expectation).If we configure "E:\Temp\$PROMOTED_NUMBER" as Remote File Location, this will be expanded (eg.) "E:\Temp\42".Sorry - I'm not sure, whether this (assumed) expansion takes place in older versions of this plugin(s) or this behaviour is a regression ...Best regards from Salzburg,Markus
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39497) No recursive expansion in promoted build
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-39497 No recursive expansion in promoted build Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 2016/Nov/04 9:12 AM Environment: Jenkins 2.25 (on Windows Server 2008 R2 x64), envinject 1.93.1, promoted-builds 2.27 Priority: Major Reporter: GMC Software Development B Corporate We have determined a problem with using an environment-variable, which are defined by using another variable (Ie. recursive expansion) in a promoted build. Following (minimal) scenario: a) Inject environment variable Output2=E:\\Temp$PROMOTED_NUMBER ... and the console shows ... [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content Output=E:\Temp\$PROMOTED_NUMBER b) Using this variable as Remote File Location in ArtifactDeployer (I.e., $Output) will use "E:\Temp\$PROMOTED_NUMBER" as destination-folder (what was not our expectation). If we configure "E:\Temp\$PROMOTED_NUMBER" as Remote File Location, this will be expanded (eg.) "E:\Temp\42". Sorry - I'm not sure, whether this (assumed) expansion takes place in older versions of this plugin(s) or this behaviour is a regression ... Best regards from Salzburg, Markus
[JIRA] (JENKINS-38334) Jenkins (master) hangs; high cpu-load w/o running jobs
Title: Message Title GMC Software Development B Corporate commented on JENKINS-38334 Re: Jenkins (master) hangs; high cpu-load w/o running jobs After some further investigations, I think that this issue may relates to (or caused by) JENKINS-33358 (Groovy and PermGen memory leak); I.e., after setting Java-property -Dgroovy.use.classvalue=true our origin problem (CPU-load, unusable UI after a few days) seems to be fixed. Additionally the Java-process does not occupy as much memory (over a few days). 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-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title
GMC Software Development B Corporate edited a comment on JENKINS-38225
Re: TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Okay, I've tested some variations of the bind-DN (CN-notation, only display-name, user principal name), and there were no noticeable differences.I think, the problem is that in case of an account like CN=user1,OU=_Users,DC=root,DC=local the result of tokengroups-lookup{ { noformat} Looking up group of CN=user1,OU=_Users,DC=root,DC=local {noformat } } will contain also the SIDs of groups, which are also located in subx.local.But the follow-up query to determine these group-names by{ { noformat} Sep 19, 2016 9:39:18 AM FINER hudson.plugins.active_directory.LDAPSearchBuildersearching (|(objectSid={0})(objectSid={1})(objectSid={2})(objectSid={3})(objectSid={4})(objectSid={5})(objectSid={6})(objectSid={7})(objectSid={8})(objectSid={9})(objectSid={10})(objectSid={11})(objectSid={12})(objectSid={13})(objectSid={14})(objectSid={15})(objectSid={16})(objectSid={17})(objectSid={18})(objectSid={19})(objectSid={20})(objectSid={21})(objectSid={22})(objectSid={23})(objectSid={24})(objectSid={25})(objectSid={26})(objectSid={27})(objectSid={28})(objectSid={29})(objectSid={30})(objectSid={31})(objectSid={32})(objectSid={33})(objectSid={34})(objectSid={35})(objectSid={36})(objectSid={37})(objectSid={38}))[[B@11f25a48, [B@242109d6, [B@40b7621f, [B@10450821, [B@1366307b, [B@3f25e478, [B@44f9de19, [B@7cc5d2a7, [B@5e02d0ac, [B@4e14f930, [B@4497effd, [B@16954d22, [B@5e5a68ec, [B@376ed76e, [B@4cfd3e79, [B@703d9699, [B@7d2d8d7a, [B@3cb9f016, [B@19120f0e, [B@507cbeb, [B@1450d06c, [B@679aabb0, [B@6ef9a232, [B@559a7495, [B@47db0dfa, [B@752ee99a, [B@56e53d3f, [B@50ddd5aa, [B@4ff6b696, [B@4d96f4cb, [B@32e52483, [B@c2bc7f0, [B@761382e5, [B@c591040, [B@1703ec74, [B@4545ad23, [B@2fab1bc4, [B@6bb4d561, [B@635ce42f] in DC=root,DC=local using {java.naming.referral=follow, java.naming.ldap.version=3, java.naming.security.principal=Svc_LDAPQuery@root,local, java.naming.ldap.attributes.binary=tokenGroups objectSid, java.naming.provider.url="" com.sun.jndi.ldap.read.timeout=6, java.naming.security.credentials=…} with scope 2 returning [cn]Sep 19, 2016 9:39:18 AM FINE hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProviderCN=user1,OU=_Users,DC=root,DC=local is a member of cn: Users {noformat } } is limited to scope DC=root,DC=local !I.e., Login with CN=user1,OU=_Users,DC=root,DC=local is permitted, but groups (which this account is member of) in our resource-domain (subx.local) are not determined, because "only" group-names of the same domain (like the user-account) are found.In our case, login or users in DC=root,DC=local and DC=subx,DC=local is permitted, but jenkins permissions are applied, if the account is memberof the (universal) group "Jenkins-Group" (CN=Jenkins-Group,CN=_Users,DC=subx,DC=local); Recursive lookup is able to determine this setup.Best regards,Markus
[JIRA] (JENKINS-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title
GMC Software Development B Corporate commented on JENKINS-38225
Re: TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Okay, I've tested some variations of the bind-DN (CN-notation, only display-name, user principal name), and there were no noticeable differences. I think, the problem is that in case of an account like CN=user1,OU=_Users,DC=root,DC=local the result of tokengroups-lookup Looking up group of CN=user1,OU=_Users,DC=root,DC=local will contain also the SIDs of groups, which are also located in subx.local. But the follow-up query to determine these group-names by {{Sep 19, 2016 9:39:18 AM FINER hudson.plugins.active_directory.LDAPSearchBuilder searching (|(objectSid= {0} )(objectSid= {1} )(objectSid= {2} )(objectSid= {3} )(objectSid= {4} )(objectSid= {5} )(objectSid= {6} )(objectSid= {7} )(objectSid= {8} )(objectSid= {9} )(objectSid= {10} )(objectSid= {11} )(objectSid= {12} )(objectSid= {13} )(objectSid= {14} )(objectSid= {15} )(objectSid= {16} )(objectSid= {17} )(objectSid= {18} )(objectSid= {19} )(objectSid= {20} )(objectSid= {21} )(objectSid= {22} )(objectSid= {23} )(objectSid= {24} )(objectSid= {25} )(objectSid= {26} )(objectSid= {27} )(objectSid= {28} )(objectSid= {29} )(objectSid= {30} )(objectSid= {31} )(objectSid= {32} )(objectSid= {33} )(objectSid= {34} )(objectSid= {35} )(objectSid= {36} )(objectSid= {37} )(objectSid= {38} ))[[B@11f25a48, [B@242109d6, [B@40b7621f, [B@10450821, [B@1366307b, [B@3f25e478, [B@44f9de19, [B@7cc5d2a7, [B@5e02d0ac, [B@4e14f930, [B@4497effd, [B@16954d22, [B@5e5a68ec, [B@376ed76e, [B@4cfd3e79, [B@703d9699, [B@7d2d8d7a, [B@3cb9f016, [B@19120f0e, [B@507cbeb, [B@1450d06c, [B@679aabb0, [B@6ef9a232, [B@559a7495, [B@47db0dfa, [B@752ee99a, [B@56e53d3f, [B@50ddd5aa, [B@4ff6b696, [B@4d96f4cb, [B@32e52483, [B@c2bc7f0, [B@761382e5, [B@c591040, [B@1703ec74, [B@4545ad23, [B@2fab1bc4, [B@6bb4d561, [B@635ce42f] in DC=root,DC=local using {java.naming.referral=follow, java.naming.ldap.version=3, java.naming.security.principal=Svc_LDAPQuery@root,local, java.naming.ldap.attributes.binary=tokenGroups objectSid, java.naming.provider.url="" com.sun.jndi.ldap.read.timeout=6, java.naming.security.credentials=…} with scope 2 returning [cn] Sep 19, 2016 9:39:18 AM FINE hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider CN=user1,OU=_Users,DC=root,DC=local is a member of cn: Users }} is limited to scope DC=root,DC=local ! I.e., Login with CN=user1,OU=_Users,DC=root,DC=local is permitted, but groups (which this account is member of) in our resource-domain (subx.local) are not determined, because "only" group-names of the same domain (like the user-account) are found. In our case, login or users in DC=root,DC=local and DC=subx,DC=local is permitted, but jenkins permissions are applied, if the account is member of the (universal) group "Jenkins-Group" (CN=Jenkins-Group,CN=_Users,DC=subx,DC=local); Recursive lookup is able to determine this setup. Best regards, Markus
[JIRA] (JENKINS-38334) Jenkins (master) hangs; high cpu-load w/o running jobs
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-38334 Jenkins (master) hangs; high cpu-load w/o running jobs Issue Type: Bug Assignee: Unassigned Attachments: ThreadDump.txt Components: core Created: 2016/Sep/19 5:41 AM Environment: Windows Server 2008 R2 x64, Java Server JRE 1.8.0_101 Labels: performance Priority: Critical Reporter: GMC Software Development B Corporate Hi, Since upgrade to Jenkins 2 (LTS 2.7.2, 2.7.3 and also with 2.22) there's a performance-issue at the Jenkins-master after about 2-4 days: The UI hangs (loading needs 5 or more minutes) and the Java-process needs about 50-99 percent CPU. It's necessary to kill the affected Java-process and to restart the Jenkins-service to re-establish our Jenkins (-farm). By "Debugging" the Java-process (with Visual Studio native remote-debugging) I have seen, that there are 1-2 *) WIN32-Threads with highest priority, which are running without noticeable yield/sleep (and occupy almost one core - of two). *) Sometimes there is only one of this running thread and the jenkins-master will response with respond with a delay of minutes; In other cases, there are two this (CPU-occupying) threads and jenkins is unusable ... Currently, we are using Jenkins 2.22 with following installed plugins:
[JIRA] (JENKINS-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title GMC Software Development B Corporate commented on JENKINS-38225 Re: TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD) Hi! We have set bindName "cn=LDAP QUERY,cn=Users,dc=root,dc=local"; Note: same account (with same pwd) also exists in domain subx.local! Best regards, Markus 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-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-38225 TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD) Change By: GMC Software Development B Corporate I have tested the tokengroups group-lookup strategy of the (newest) Active Directory Plugin in our AD-environment. Our AD is setup as forest, were some users are located in the root-domain (e.g., root.local), but most user-accounts, security-groups and computers are located in the second resource-domain (e.g., subx.local).Therefore, the plugin is currently configured with* Domain Name = "subx.local,root.local",* Domain controller = "dc1.subx.local:3268,dc2.subx.local:3268"* Group Membership Lookup Strategy = "RECURSIVE"With this configuration, login "against" a local group of subx.local by using an account of root.local (which is member of the local group) is permitted.If I change the the group-lookup strategy to "TOKENGROUPS", the login fails *) .. and after some tests (with logging 'FINE'), I've determined (or assume), that:* Searching for the user-object and login (with credentials) is successful,* also getting the tokengroups-list (SIDs) will contain local, universal groups of the subx.local (which DC was asked),* But the the name-translation of the tokengroups-SIDs afterwards, is limited to the domain (by Bind-DN) of the user-object. Therefore, the security-groups of our resource-domain (subx.local) were not found! *) More concrete:Login with an account of the resource-domain (subx.local) is still successful; an much faster.The failure/problem occurs only with accounts of the "extra" root-domain. Assuming, that my findings/assumptions are correct: It is possible to change the implementation, that groups of "different" (but also configured/permitted domain), are permitted?Best regards from Salzburg,Markus Add Comment
[JIRA] (JENKINS-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-38225 TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD) Change By: GMC Software Development B Corporate I have tested the tokengroups group-lookup strategy of the (newest) Active Directory Plugin in our AD-environment. Out Our AD is setup as forest, were some users are located in the root-domain (e.g., root.local), but most user-accounts, security-groups and computers are located in the second resource -domain (e.g., subx.local).Therefore, the plugin is currently configured with* Domain Name = "subx.local,root.local",* Domain controller = "dc1.subx.local:3268,dc2.subx.local:3268"* Group Membership Lookup Strategy = "RECURSIVE"With this configuration, login "against" a local group of subx.local and by using an account of root.local (which is member of the local group) was is permitted.If I change the the group-lookup strategy to "TOKENGROUPS", the login fails .. and after some tests (with logging 'FINE'), I've determined (or assume), that:* Searching for the user-object and login (with credentials) is successful,* also getting the tokengroups-list (SIDs) will contain local, universal groups of the subx.local (which DC was asked),* But the the name-translation of the tokengroups-SIDs afterwards, is limited to the domain (by Bind-DN) of the user-object. Therefore, the security-groups of our resource-domain (subx.local) were not found!Assuming, that my findings/assumptions are correct: It is possible to change the implementation, that groups of "different" (but also configured/permitted domain), are permitted?Best regards from Salzburg,Markus Add Comment
[JIRA] (JENKINS-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-38225 TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD) Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Sep/15 5:55 AM Environment: Windows Server 2008 R2 (x64), Active Directory plugin 1.48 Priority: Minor Reporter: GMC Software Development B Corporate I have tested the tokengroups group-lookup strategy of (newest) Active Directory Plugin in our AD-environment. Out AD is setup as forest, were some users are located in the root-domain (e.g., root.local), but most user-accounts, security-groups and computers are located in the second-domain (e.g., subx.local). Therefore, the plugin is currently configured with Domain Name = "subx.local,root.local", Domain controller = "dc1.subx.local:3268,dc2.subx.local:3268" Group Membership Lookup Strategy = "RECURSIVE" With this configuration, login "against" a local group of subx.local and using an account of root.local (which is member of the local group) was permitted. If I change the the group-lookup strategy to "TOKENGROUPS", the login fails ... ... and after some tests (with logging 'FINE'), I've determined (or assume), that: Searching for the user-object and login (with credentials) is successful,
[JIRA] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title GMC Software Development B Corporate edited a comment on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects Issue JENKINS-35330 describes that the content of "List subversion tags and more" and branch parameters of the Git plugin are not passed to the child jobs (I.e., als as "null"). I think, the the applied fix should be revised for this types of parameters. Therefore, I've setup a link between these two issues and re-opened this issue ...Best regards from Salzburg,Markus 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-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: GMC Software Development B Corporate Comment: Issue JENKINS-35330 describes that the content of "List subversion tags and more" and branch parameters of the Git plugin are not passed to the child jobs (I.e., als "null"). I think, the the applied fix should be revised for this types of parameters. Therefore, I've setup a link between these two issues and re-opened this issue ...Best regards from Salzburg,Markus 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-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title GMC Software Development B Corporate reopened an issue Issue JENKINS-35330 describes that the content of "List subversion tags and more" and branch parameters of the Git plugin are not passed to the child jobs (I.e., als "null"). I think, the the applied fix should be revised for this types of parameters. Therefore, I've setup a link between these two issues and re-opened this issue ... Best regards from Salzburg, Markus Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: GMC Software Development B Corporate Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title GMC Software Development B Corporate commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects Issue JENKINS-35330 describes that the content of "List subversion tags and more" and branch parameters of the Git plugin are not passed to the child jobs (I.e., als "null"). I think, the the applied fix should be revised for this types of parameters. Therefore, I've setup a link between these two issues and re-opened this issue ... Best regards from Salzburg, Markus 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-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title GMC Software Development B Corporate assigned an issue to Antonio Muñiz Jenkins / JENKINS-35330 Matrix plugin forwards subversion tag parameter value as null Change By: GMC Software Development B Corporate Assignee: Kohsuke Kawaguchi Antonio Muñiz 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] [matrix-project-plugin] (JENKINS-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title GMC Software Development B Corporate commented on JENKINS-35330 Re: Matrix plugin forwards subversion tag parameter value as null Same issue after upgrading to Matrix Project Plugin 1.7, on: Jenkins 1.656 (Windows Server 2008 R2, JRE Server 1.8.0_71), and Subversion Plugin 2.5.7 IMHO, bumped priority to Critical, because this issue breaks jobs. Best regards, Markus 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] [matrix-project-plugin] (JENKINS-35330) Matrix plugin forwards subversion tag parameter value as null
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-35330 Matrix plugin forwards subversion tag parameter value as null Change By: GMC Software Development B Corporate Priority: Major Critical 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] [email-ext-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title GMC Software Development B Corporate commented on JENKINS-33612 Re: Provision error (Tried proxying due circular dependency) reported at startup Hi Alex! I've tried your snapshot-artefact (on my test-wrks) and it works; I.e., this issue gone away. Thanks for your prompt response! BR, Markus 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] [email-ext-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-33612 Provision error (Tried proxying due circular dependency) reported at startup Change By: GMC Software Development B Corporate Component/s: email-ext-plugin 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] [emailext-template-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title GMC Software Development B Corporate commented on JENKINS-33612 Re: Provision error (Tried proxying due circular dependency) reported at startup Hi, to reproduce this issue, I've setup a "fresh" installation of Jenkins 1.655 on a test-workstation with Windows 7 (x64) - to check, whether "it" also occurs on another machine with a minimal count of installed plugins. After updating the plugins (as currently released) and installing the Email-ext Template Plugin (+ Email-ext plugin) following (enabled) plugins are used: Plugin version ant 1.2 antisamy-markup-formatter 1.3 cloudbees-folder 5.6 credentials 1.26 cvs 2.12 email-ext
[JIRA] [emailext-template-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-33612 Provision error (Tried proxying due circular dependency) reported at startup Minimal configuration-file (Extended Email Templates), causing this issue on startup/restart. Change By: GMC Software Development B Corporate Attachment: org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher.xml 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] [emailext-template-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-33612 Provision error (Tried proxying due circular dependency) reported at startup Issue Type: Bug Assignee: Alex Earl Components: emailext-template-plugin Created: 2016/Mar/17 9:37 AM Environment: Jenkins version 1.652 on Windows Server 2008 R2 (x64), Email Extension Template Plugin 0.4, Email Extension Plugin 2.41.3 Priority: Minor Reporter: GMC Software Development B Corporate Hi, On start-up of out jenkins-master, I've got following Email Extension Template Plugin related entry in the Jenkins Log: Mar 16, 2016 1:08:18 PM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate Key[type=org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Tried proxying org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher$DescriptorImpl to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at
[JIRA] [emailext-template-plugin] (JENKINS-33612) Provision error (Tried proxying due circular dependency) reported at startup
Title: Message Title
GMC Software Development B Corporate updated an issue
Jenkins / JENKINS-33612
Provision error (Tried proxying due circular dependency) reported at startup
Change By:
GMC Software Development B Corporate
Hi,On start-up of out our jenkins-master, I've got following Email Extension Template Plugin related entry in the Jenkins Log:{noformat}Mar 16, 2016 1:08:18 PM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorFailed to instantiate Key[type=org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher$DescriptorImpl, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Guice provision errors:1) Tried proxying org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher$DescriptorImpl to support a circular dependency, but it is not an interface.1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:389) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1231) at hudson.plugins.emailext.plugins.recipients.UpstreamComitterRecipientProvider.(UpstreamComitterRecipientProvider.java:36) at sun.misc.Unsafe.allocateInstance(Native Method) at com.thoughtworks.xstream.converters.reflection.SunLimitedUnsafeReflectionProvider.newInstance(SunLimitedUnsafeReflectionProvider.java:76) at hudson.util.RobustReflectionConverter.instantiateNewInstance(RobustReflectionConverter.java:395) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:228) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:80) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at
