[JIRA] (JENKINS-61294) Jenkins node disconnects frequently because of that job fails.
Title: Message Title Markus Winter commented on JENKINS-61294 Re: Jenkins node disconnects frequently because of that job fails. Fresstyle jobs will fail when the connection from master to agent is lost. Try using pipeline jobs instead. So the question is why you loose connection that frequently, maybe your network is unreliable. 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.204871.1583165063000.13139.1585162800293%40Atlassian.JIRA.
[JIRA] (JENKINS-58886) Project base security matrix allows wrong group of users access
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-58886 Project base security matrix allows wrong group of users access Change By: Markus Winter Component/s: matrix-auth-plugin 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.201219.1565517127000.9030.1580418240226%40Atlassian.JIRA.
[JIRA] (JENKINS-60429) Replace @ symbol in workspace suffix path for parallel builds
Title: Message Title Markus Winter closed an issue as Not A Defect Jenkins / JENKINS-60429 Replace @ symbol in workspace suffix path for parallel builds Change By: Markus Winter Status: Open Closed Resolution: Not A Defect 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.203501.1576018208000.9007.1580416560351%40Atlassian.JIRA.
[JIRA] (JENKINS-59628) Retrieve currently logged-in user from shared library programmatically
Title: Message Title Markus Winter commented on JENKINS-59628 Re: Retrieve currently logged-in user from shared library programmatically As already mentioned in the other tickets there is no user associated with a build when it was triggered by an scm poll or by a schedule or a github event. And when you say logged-in user, which one you mean when you have more than one user accessing your Jenkins at the same time? And when you use the REST API you need to authenticate probably for which you have to provide a user. And then it will return exactly this user as the logged in user. The only use case I see is when you have a pipeline step waiting for user input. But then when a user clicks on a button you have a http request with a user. 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.202272.1570031559000.8830.1580376960127%40Atlassian.JIRA.
[JIRA] (JENKINS-60429) Replace @ symbol in workspace suffix path for parallel builds
Title: Message Title Markus Winter commented on JENKINS-60429 Re: Replace @ symbol in workspace suffix path for parallel builds Set the property hudson.slaves.WorkspaceList at startup. See https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties 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.203501.1576018208000.8632.1580343780138%40Atlassian.JIRA.
[JIRA] (JENKINS-60503) What plugin causes the error
Title: Message Title Markus Winter commented on JENKINS-60503 Re: What plugin causes the error the stacktrace includes net.bull.javamelody so I would guess it is the monitoring plugin 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.203594.1576504952000.8630.1580343300151%40Atlassian.JIRA.
[JIRA] (JENKINS-60684) Job shown twice and creates duplicate folder in Windows
Title: Message Title Markus Winter commented on JENKINS-60684 Re: Job shown twice and creates duplicate folder in Windows I doubt it is possible on Windows to create 2 entries in a folder that have the same name. my guess would be that you really have 2 different jobs with slightly different name. Maybe something like job0 and jobO or maybe with different unicode characters that are displayed the same way. Is the job config of both jobs identical? 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.203928.1578468961000.8625.1580342640227%40Atlassian.JIRA.
[JIRA] (JENKINS-60903) Include information about number of CPUs and memory in the node view
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-60903 Include information about number of CPUs and memory in the node view Issue Type: New Feature Assignee: lifeless Components: platformlabeler-plugin Created: 2020-01-29 12:54 Priority: Minor Reporter: Markus Winter A node property can display additional information in a dedicated jelly. We could use this to display additional information like number of CPUs and installed memory for the machines which are fetched when getting the OS information. Add Comment
[JIRA] (JENKINS-60830) job duration does not include the time spent in after finalized steps
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-60830 job duration does not include the time spent in after finalized steps Issue Type: New Feature Assignee: Unassigned Components: core Created: 2020-01-21 12:03 Priority: Minor Reporter: Markus Winter The duration of a job is calculated directly after the normal steps and the post build steps are finished. But it doesn't include those post build steps, that have needsToRunAfterFinalized set to true and also any runlisteners of oncompleted and on finalized calls are not included. I propose to add an additional field totalDuration that is set as the very last thing in the Run class Add Comment
[JIRA] (JENKINS-54689) Incorrect display build duration time
Title: Message Title Markus Winter commented on JENKINS-54689 Re: Incorrect display build duration time Technically the duration is the time the job started until it finished. We have pipeline jobs here, they start without the need of an executor, so they usually do not spent any time in the queue. So I assume the job was waiting in between to get a free slot on an agent. So what me might need is an additional column with Execution time. 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.195483.1542586104000.3169.1579606740185%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Markus Winter commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat There is already a pull request open that fixes the issue 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.200271.1561558166000.12603.1576678620413%40Atlassian.JIRA.
[JIRA] (JENKINS-59904) NPE when calling logout without cookie
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-59904 NPE when calling logout without cookie Change By: Markus Winter Using some script we called the logout url of Jenkins. This lead to a null pointer exception as the code to search for stale session cookies is not performing a null check. java.lang.NullPointerException at hudson.security.SecurityRealm.clearStaleSessionCookies(SecurityRealm.java:328) at hudson.security.SecurityRealm.doLogout(SecurityRealm.java:296) at jenkins.model.Jenkins.doLogout(Jenkins.java:4063) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) How to reproduce:curl [https://ci.jenkins.io/logout] or open a browser, delete all cookies and the browse open the same url Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59904) NPE when calling logout without cookie
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-59904 NPE when calling logout without cookie Change By: Markus Winter Using some script we called the logout url of Jenkins. This lead to a null pointer exception as the code to search for stale session cookies is not performing a null check. java.lang.NullPointerException at hudson.security.SecurityRealm.clearStaleSessionCookies(SecurityRealm.java:328) at hudson.security.SecurityRealm.doLogout(SecurityRealm.java:296) at jenkins.model.Jenkins.doLogout(Jenkins.java:4063) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) How to reproduce:curl [https://ci.jenkins.io/logout] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59904) NPE when calling logout without cookie
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-59904 NPE when calling logout without cookie Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-23 14:44 Environment: Jenkins 2.190.1 Priority: Minor Reporter: Markus Winter Using some script we called the logout url of Jenkins. This lead to a null pointer exception as the code to search for stale session cookies is not performing a null check. java.lang.NullPointerException at hudson.security.SecurityRealm.clearStaleSessionCookies(SecurityRealm.java:328) at hudson.security.SecurityRealm.doLogout(SecurityRealm.java:296) at jenkins.model.Jenkins.doLogout(Jenkins.java:4063) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Markus Winter edited a comment on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat The plugin has a dependecy tocom.atlassianant-filesystem-taskswhich has a dependency to a very old jna and org.jruby.ext.posix.jna-posixI guess the LocalCopy class needs to be reimplemented without the Atlassian stuff to be able to fix it. Or shade the dependency to jna as proposed in JENKINS-58207Staying on old jna in Jenkins core is causing issues when trying to connect AIX machines with certain JDKs (see JENKINS-57515) 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.200271.1561558166000.4967.1569409920425%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Markus Winter commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat The plugin has a dependecy to com.atlassian ant-filesystem-tasks which has a dependency to a very old jna and org.jruby.ext.posix.jna-posix I guess the LocalCopy class needs to be reimplemented without the Atlassian stuff to be able to fix it. Staying on old jna in Jenkins core is causing issues when trying to connect AIX machines with certain JDKs (see JENKINS-57515) 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.200271.1561558166000.4957.1569409680285%40Atlassian.JIRA.
[JIRA] (JENKINS-58847) After renaming project logs of runs prior to rename are not found
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-58847 After renaming project logs of runs prior to rename are not found Issue Type: Bug Assignee: Jesse Glick Components: pipeline-cloudwatch-logs-plugin Created: 2019-08-07 12:05 Priority: Major Reporter: Markus Winter Without verifying this, I think if the project gets renamed or moved, the logs will no longer be found. Reason is that the logStreamNameBase is basically the projects fullName, that changes on rename or move. A solution would be to use the unique id plugin Add Comment
[JIRA] (JENKINS-58816) GraphListener method when a FlowNode has finished
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-58816 GraphListener method when a FlowNode has finished Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-08-05 15:00 Priority: Minor Reporter: Markus Winter It would be nice if we can be notified when a node in the flowgraph has finished by adding a method `GraphListener.onNodeFinished(FlowNode node)` For AtomNode, we only get notified in the GraphListener before the node starts execution but never when it ends. For steps that have a block, we have the dedicated BlockEndNode but at the time it is called, the status of the node is not yet set. While we can use the getParents() of a FlowNode and process the parent nodes, it means we are not able to react in a timely manner to the end of a node. E.g. parallel branches would only be processed once the complete parallel step is finished and the FlowEndNode can never be processed this way. Add Comment
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Markus Winter commented on JENKINS-52189 Re: GraphListener does not receive FlowStartNode Having the same issue with the missed FlowStartNode Any idea when the fixes will be released? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191946.1530020805000.5396.1564664040172%40Atlassian.JIRA.
[JIRA] (JENKINS-58703) creating folder via XML results in double property
Title: Message Title
Markus Winter updated an issue
Jenkins / JENKINS-58703
creating folder via XML results in double property
Change By:
Markus Winter
Create folder by posting attached xml to createItem?name=testFolderThis results in the following config.xml being generated.{code:java} test hudson.model.Item.Read:authenticated... {code}As you can see we have 2 AuthorizationMatrixProperty elements.The problem is that the ItemListener adds the AuthorizationMatrixProperty even when it already existed (see line 244 [code|https://github.com/jenkinsci/matrix-auth-plugin/blob/8c7b7bcec67a03ab73498486fc2029b2b886541d/src/main/java/com/cloudbees/hudson/plugins/folder/properties/AuthorizationMatrixProperty.java#L244]) This is not causing issues but is irritating.Saving via the UI without changing anything resolves the issue.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200992.1564395718000.2608.1564395960159%40Atlassian.JIRA.
[JIRA] (JENKINS-58703) creating folder via XML results in double property
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-58703 creating folder via XML results in double property Change By: Markus Winter Environment: Jenkins 2.164.3 matrix auth plugin 2.4.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200992.1564395718000.2606.1564395900941%40Atlassian.JIRA.
[JIRA] (JENKINS-58703) creating folder via XML results in double property
Title: Message Title
Markus Winter updated an issue
Jenkins / JENKINS-58703
creating folder via XML results in double property
Change By:
Markus Winter
Create folder by posting attached xml to createItem?name=testFolderThis results in the following config.xml being generated.{code:java} < ?xml version='1.1' encoding='UTF-8'?> test < properties>hudson.model.Item.Read:authenticated ... {code}As you can see we have 2 AuthorizationMatrixProperty elements.The problem is that the ItemListener adds the AuthorizationMatrixProperty even when it already existed (see line 244 [code|https://github.com/jenkinsci/matrix-auth-plugin/blob/8c7b7bcec67a03ab73498486fc2029b2b886541d/src/main/java/com/cloudbees/hudson/plugins/folder/properties/AuthorizationMatrixProperty.java#L244])
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200992.1564395718000.2604.1564395840564%40Atlassian.JIRA.
[JIRA] (JENKINS-58703) creating folder via XML results in double property
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-58703 creating folder via XML results in double property Issue Type: Bug Assignee: Daniel Beck Attachments: folder.xml Components: matrix-auth-plugin Created: 2019-07-29 10:21 Environment: Jenkins 2.164.3 Priority: Minor Reporter: Markus Winter Create folder by posting attached xml to createItem?name=testFolder This results in the following config.xml being generated. "org.jenkinsci.plugins.matrixauth.inheritance.NonInheritingStrategy"/> hudson.model.Item.Read:authenticated "../com.cloudbees.hudson.plugins.folder.properties.AuthorizationMatrixProperty"/> As you can see we have 2 AuthorizationMatrixProperty elements. The problem is that the ItemListener adds the AuthorizationMatrixProperty even when it already existed (see line 244 code)
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title Markus Winter commented on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO plugin itself packs jna-4.5.1.jar and jna-platform-4.5.1.jar via waffle Due to classloading the plugins sees the newer jna-5.3.1.jar from Jenkins but the old jna-platform-4.5.1.jar which leads to this error. Possible solutions: plugin first classloading add explicit dependency to jna and jna-platform (seems waffle itself doesn't need code adjustments, so this might work) wait for waffle to release new version (current head also uses 5.3.1 of jna, but this is not yet released) Jenkins core also packs jna-platform (though it seems it doesn't need it) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.9297.1561551720557%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57515) AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-57515 AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so Change By: Markus Winter Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199418.1558076672000.7137.1561366020195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57855) PathRemover unable to delete folder with read only flag on Windows
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-57855 PathRemover unable to delete folder with read only flag on Windows Change By: Markus Winter Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199814.1559723142000.7135.1561365960061%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44414) Lost ssh connection is not recognized
Title: Message Title Markus Winter resolved as Fixed fixed Jenkins / JENKINS-44414 Lost ssh connection is not recognized Change By: Markus Winter Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182240.1495451398000.23249.1559894760731%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45095) retrigger doesn't work when deleting build from Queue
Title: Message Title Markus Winter resolved as Fixed was fixed in 2.25.0 Jenkins / JENKINS-45095 retrigger doesn't work when deleting build from Queue Change By: Markus Winter Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183189.1498203664000.23240.1559894700529%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57515) AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so
Title: Message Title Markus Winter commented on JENKINS-57515 Re: AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so I have the same issue. So I opened a pull request https://github.com/jenkinsci/jenkins/pull/4060 that will update the JNA library to 5.3.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199418.1558076672000.22798.1559833920181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57855) PathRemover unable to delete folder with read only flag on Windows
Title: Message Title
Markus Winter updated an issue
Jenkins / JENKINS-57855
PathRemover unable to delete folder with read only flag on Windows
Change By:
Markus Winter
Since updating to Jenkins core to 2.164.3 we run into issues that builds running on windows agents were not able do delete certain folders when checking out with git.We always get an access denied:* *{code:java} 16:53:25 * java.nio.file.AccessDeniedException: d:\701\w\ 1bgf889vez project \cache\dependencies\clients\ant-1.9.4-bin\bin * 16:53:25 * at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83) * 16:53:25 * at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) * 16:53:25 * at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) * 16:53:25 * at sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269) * 16:53:25 * at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) * 16:53:25 * at java.nio.file.Files.deleteIfExists(Files.java:1165) * 16:53:25 * at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:233) {code} Trying a _rd _ on the command line shows the same problem. But _rd /s _ works.After analysis we found the problem is that some build process creates folders that have the read only flag set. {code:java}D:\>attrib d:\701\w\project\cache\dependencies\clients\ant-1.9.4-bin\bin Rd:\701\w\project\cache\dependencies\clients\ant-1.9.4-bin\bin{code} The PathRemover tries to resolve this by calling_path.toFile().setWritable(true);_on each file/folder it can't delete initially.But this method will not remove the read only flag on a windows folder.The soluition solution is to use_Files.setAttribute(path, "dos:readonly", false);_
Add Comment
[JIRA] (JENKINS-57855) PathRemover unable to delete folder with read only flag on Windows
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-57855 PathRemover unable to delete folder with read only flag on Windows Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-06-05 08:25 Environment: Jenkins 2.164.3 Priority: Blocker Reporter: Markus Winter Since updating to Jenkins core to 2.164.3 we run into issues that builds running on windows agents were not able do delete certain folders when checking out with git. We always get an access denied: 16:53:25 java.nio.file.AccessDeniedException: d:\701\w\1bgf889vez\cache\dependencies\clients\ant-1.9.4-bin\bin*16:53:25* at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83)16:53:25 at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)16:53:25 at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)16:53:25 at sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269)16:53:25 at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108)16:53:25 at java.nio.file.Files.deleteIfExists(Files.java:1165)16:53:25 at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:233) Trying a rd on the command line shows the same problem. But rd /s works. After analysis we found the problem is that some build process creates folders that have the read only flag set. The PathRemover tries to resolve this by calling path.toFile().setWritable(true); on each file/folder it can't delete initially. But this method will not remove the read only flag on a windows folder. The soluition is to use Files.setAttribute(path, "dos:readonly", false);
[JIRA] (JENKINS-57107) SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p)
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-57107 SafeURLStreamHandler does not overwrite openConnection(URL u, Proxy p) Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-04-18 10:39 Priority: Major Reporter: Markus Winter In a plugin I tried to open a connection with proxy on an URL object that has the SafeURLStreamHandler as its handler. url.openConnection(proxy) SafeURLStreamHandler is not overwriting openConnection(URL u, Proxy p) and due to that an UnsupportedOperationException exception is thrown. Add Comment
[JIRA] (JENKINS-50568) Receiving Workers thread are not reconfigurable without Jenkins restart
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-50568 Receiving Workers thread are not reconfigurable without Jenkins restart Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 2018-04-04 12:14 Environment: gerrit-trigger-plugin 2.27.5 Priority: Major Reporter: Markus Winter We today had the problem that the receiving workers queue was somehow stuck and we have piled up 800k events. After reconnecting the event listener events were processed again, but with only 8 threads and 18k jobs it would take over 10h to process all events (even though 99% of the events are replication events which are not of interest for us). Changing the # of receiving worker threads has no effect. Looking at the code this requires a restart of Jenkins. JENKINS-20120 only solved the thing for the sending queue Add Comment
[JIRA] (JENKINS-44568) Gerrit Trigger version 23.2 fails to trigger Jenkins jobs on Jenkins version 2.46.3!!!
Title: Message Title Markus Winter assigned an issue to rsandell Jenkins / JENKINS-44568 Gerrit Trigger version 23.2 fails to trigger Jenkins jobs on Jenkins version 2.46.3!!! Change By: Markus Winter Assignee: Markus Winter rsandell 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-44568) Gerrit Trigger version 23.2 fails to trigger Jenkins jobs on Jenkins version 2.46.3!!!
Title: Message Title Markus Winter commented on JENKINS-44568 Re: Gerrit Trigger version 23.2 fails to trigger Jenkins jobs on Jenkins version 2.46.3!!! The fix is in since 2.25.0 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-44568) Gerrit Trigger version 23.2 fails to trigger Jenkins jobs on Jenkins version 2.46.3!!!
Title: Message Title Markus Winter assigned an issue to Markus Winter Jenkins / JENKINS-44568 Gerrit Trigger version 23.2 fails to trigger Jenkins jobs on Jenkins version 2.46.3!!! Change By: Markus Winter Assignee: rsandell Markus Winter 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-41128) createItem in View not working when posting xml
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-41128 createItem in View not working when posting xml Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Jan/17 12:40 PM Priority: Major Reporter: Markus Winter After the issue JENKINS-19142 was implemented it is no longer possible, to create a Job in a View by posting the xml in the url .../view//createItem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40772) plugin not compatible to folders plugin version 4.10 and older
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-40772 plugin not compatible to folders plugin version 4.10 and older Issue Type: Bug Assignee: Magnus Sandberg Components: prioritysorter-plugin Created: 2017/Jan/03 12:30 PM Environment: Jenkins 1.580.3 Folders plugin 4.10 Priority: Major Reporter: Markus Winter The priority sorter plugin is currently built againt Jenkins 1.580. But also againt folders plugin version 5.0 Folders plugin 5.0 has as minimum version 1.609.1 of jenkins. I have a jenkins on 1.580.3 and folders plugin 4.10 If I enable in a jobgroup "Jobs and Folders marked for inclusion", I get the following exception when configuring a job Caused by: java.lang.NoClassDefFoundError: com/cloudbees/hudson/plugins/folder/AbstractFolder So either the plugin is fixed so it can handle also older version of the folders plugin, or the minimum required version of Jenkins is set to 1.609.1 Add Comment
[JIRA] (JENKINS-39972) Export fullName from AbstractItem to the REST API
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-39972 Export fullName from AbstractItem to the REST API Change By: Markus Winter Would be nice to have the fullName and maybe also the fullDisplayName of items exported. When using the rest API to get jobs in a folder, it is not possible to identify the projects just from the result. It is only valid in the context of the REST call. 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-39972) Export fullName from AbstractItem to the REST API
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-39972 Export fullName from AbstractItem to the REST API Issue Type: New Feature Assignee: Unassigned Components: core Created: 2016/Nov/23 2:17 PM Priority: Trivial Reporter: Markus Winter Would be nice to have the fullName of items exported. When using the rest API to get jobs in a folder, it is not possible to identify the projects just from the result. It is only valid in the context of the REST call. Add Comment This mess
[JIRA] [plugin-proposals] (JENKINS-31895) Mark many nodes as temporarily offline at once
Title: Message Title Markus Winter commented on JENKINS-31895 Re: Mark many nodes as temporarily offline at once You could write a system groovy script that takes a label _expression_ as parameter. Then you can loop over the list of nodes and take them temporarily offline. The job might wait until all nodes have finished before it ends. The script could be also used to take the nodes online again. 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] [ssh-credentials-plugin] (JENKINS-32448) Like passwords, private keys value should not be shown in edition mode
Title: Message Title Markus Winter commented on JENKINS-32448 Re: Like passwords, private keys value should not be shown in edition mode Additionally the private key should also be encrypted in the credentials.xml, like the password. 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.
