[JIRA] (JENKINS-38734) RTC environment variables to set
Title: Message Title Dorian Daumiller edited a comment on JENKINS-38734 Re: RTC environment variables to set works with rtc-buildtoolkit 6.0.2 (our server being 6.0.2) and: Jenkins 2.19.1 Pipeline 2.4Pipeline Graph Analysis Plugin 1.2Pipeline: API 2.6Pipeline: Basic Steps 2.3Pipeline: Build Step 2.3Pipeline: Groovy 2.23Pipeline: Input Step 2.5Pipeline: Job 2.8Pipeline: Milestone Step 1.1Pipeline: Multibranch 2.9.2Pipeline: Nodes and Processes 2.5Pipeline: REST API Plugin 2.2Pipeline: SCM Step 2.2Pipeline: Shared Groovy Libraries 2.4Pipeline: Stage Step 2.2Pipeline: Stage View Plugin 2.2Pipeline: Step API 2.5Pipeline: Supporting APIs 2.10 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-38734) RTC environment variables to set
Title: Message Title Dorian Daumiller commented on JENKINS-38734 Re: RTC environment variables to set works with rtc-buildtoolkit 6.0.2 (our server being 6.0.2) and: Pipeline 2.4 Pipeline Graph Analysis Plugin 1.2 Pipeline: API 2.6 Pipeline: Basic Steps 2.3 Pipeline: Build Step 2.3 Pipeline: Groovy 2.23 Pipeline: Input Step 2.5 Pipeline: Job 2.8 Pipeline: Milestone Step 1.1 Pipeline: Multibranch 2.9.2 Pipeline: Nodes and Processes 2.5 Pipeline: REST API Plugin 2.2 Pipeline: SCM Step 2.2 Pipeline: Shared Groovy Libraries 2.4 Pipeline: Stage Step 2.2 Pipeline: Stage View Plugin 2.2 Pipeline: Step API 2.5 Pipeline: Supporting APIs 2.10 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-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Dorian Daumiller updated an issue Jenkins / JENKINS-28447 CpsScmFlowDefinition does not resolve variables Change By: Dorian Daumiller Comment: Could it be that changing this introduced JENKINS-38734?I have these versions of pipeline related Plugins:Pipeline 2.4Pipeline Graph Analysis Plugin 1.2Pipeline: API 2.6Pipeline: Basic Steps 2.3Pipeline: Build Step 2.3Pipeline: Groovy 2.23Pipeline: Input Step 2.5Pipeline: Job 2.8Pipeline: Milestone Step 1.1Pipeline: Multibranch 2.9.2Pipeline: Nodes and Processes 2.5Pipeline: REST API Plugin 2.2Pipeline: SCM Step 2.2Pipeline: Shared Groovy Libraries 2.4Pipeline: Stage Step 2.2Pipeline: Stage View Plugin 2.2Pipeline: Step API 2.5Pipeline: Supporting APIs 2.10 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-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Dorian Daumiller commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables Could it be that changing this introduced JENKINS-38734? I have these versions of pipeline related Plugins: Pipeline 2.4 Pipeline Graph Analysis Plugin 1.2 Pipeline: API 2.6 Pipeline: Basic Steps 2.3 Pipeline: Build Step 2.3 Pipeline: Groovy 2.23 Pipeline: Input Step 2.5 Pipeline: Job 2.8 Pipeline: Milestone Step 1.1 Pipeline: Multibranch 2.9.2 Pipeline: Nodes and Processes 2.5 Pipeline: REST API Plugin 2.2 Pipeline: SCM Step 2.2 Pipeline: Shared Groovy Libraries 2.4 Pipeline: Stage Step 2.2 Pipeline: Stage View Plugin 2.2 Pipeline: Step API 2.5 Pipeline: Supporting APIs 2.10 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-33691) URLTrigger Plugin doesn't work in jenkins 2.0 alpha 3 when using job type Pipeline
Title: Message Title Dorian Daumiller commented on JENKINS-33691 Re: URLTrigger Plugin doesn't work in jenkins 2.0 alpha 3 when using job type Pipeline Same error for Jenkins 2.7.4 with URLTrigger Plug-in 0.41 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-38734) RTC environment variables to set
Title: Message Title Dorian Daumiller commented on JENKINS-38734 Re: RTC environment variables to set Downgrading to 2.17 worked as a workaround. But a fix would be very much appreciated. Anybody know how to debug where this comes from? 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] [workflow-plugin] (JENKINS-28183) Hard killed job's stage blocks stage in following jobs
Title: Message Title Dorian Daumiller commented on JENKINS-28183 Re: Hard killed job's stage blocks stage in following jobs Had the same issue. Worked around it like this: aborted the waiting build (forcibly) renamed the blocking build's folder on the file system saw that ```$JENKINS_HOME/org.jenkinsci.plugins.workflow.support.steps.StageStep.xml``` wasn't cleared because already a new build had started aborted the new build, too found the StageStep xml file empty and was able to restart the job. 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] [slave-status-plugin] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title Dorian Daumiller commented on JENKINS-19445 Re: Jobs randomly stuck with "building remotely on slave-name" message Can we agree on having this in LTS? 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] [slave-status-plugin] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title
Dorian Daumiller edited a comment on JENKINS-19445
Re: Jobs randomly stuck with "building remotely on slave-name" message
Deactivating the (all) monitorings on the Jenkins master did not help us. Before reconnecting the swarm client, we see this:Curiously, we also still see the monitoring in the Jenkins log: ``` {{ May 09, 2016 9:38:39 AM WARNING hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitorFailed to monitor -ed055395 for Free Swap Spacejava.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:273) at hudson.remoting.Request$1.get(Request.java:207) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:96) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305) ``` }} On the build node, amidst tons of threads, we see two that are referencing ``` {{ org.tmatesoft.svn.core.internal.util.jna ``` }} : ``` {{ pool-1-thread-2 for channel"pool-1-thread-2 for channel" Id=16 Group=main RUNNABLE at com.sun.jna.Native.initIDs(Native Method) at com.sun.jna.Native.(Native.java:148) at org.tmatesoft.svn.core.internal.util.jna.JNALibraryLoader.(JNALibraryLoader.java:50) at org.tmatesoft.svn.core.internal.util.jna.SVNWin32Util.getApplicationDataPath(SVNWin32Util.java:113) at org.tmatesoft.svn.core.internal.util.jna.SVNJNAUtil.getApplicationDataPath(SVNJNAUtil.java:196) at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.getApplicationDataPath(SVNFileUtil.java:1948) at org.tmatesoft.svn.core.wc.SVNWCUtil.getDefaultConfigurationDirectory(SVNWCUtil.java:57) at hudson.scm.SubversionSCM.createSvnAuthenticationManager(SubversionSCM.java:1055) at hudson.scm.SubversionSCM.createClientManager(SubversionSCM.java:1032) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:965) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:945) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2719) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Number of locked synchronizers = 1 - java.util.concurrent.ThreadPoolExecutor$Worker@5f599d56 ``` }} ``` {{ pool-1-thread-916 for channel"pool-1-thread-916 for channel" Id=930 Group=main RUNNABLE at org.tmatesoft.svn.core.internal.util.jna.SVNWin32Util.getApplicationDataPath(SVNWin32Util.java:113) at org.tmatesoft.svn.core.internal.util.jna.SVNJNAUtil.getApplicationDataPath(SVNJNAUtil.java:196) at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.getApplicationDataPath(SVNFileUtil.java:1948) at org.tmatesoft.svn.core.wc.SVNWCUtil.getDefaultConfigurationDirectory(SVNWCUtil.java:57) at hudson.scm.SubversionSCM.createSvnAuthenticationManager(SubversionSCM.java:1055) at hudson.scm.SubversionSCM.createClientManager(SubversionSCM.java:1032) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:965) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:945) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2719) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Sou
[JIRA] [slave-status-plugin] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title Dorian Daumiller commented on JENKINS-19445 Re: Jobs randomly stuck with "building remotely on slave-name" message Deactivating the (all) monitorings on the Jenkins master did not help us. Before reconnecting the swarm client, we see this: Curiously, we also still see the monitoring in the Jenkins log: ``` May 09, 2016 9:38:39 AM WARNING hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor Failed to monitor -ed055395 for Free Swap Space java.util.concurrent.TimeoutException at hudson.remoting.Request$1.get(Request.java:273) at hudson.remoting.Request$1.get(Request.java:207) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:96) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305) ``` On the build node, amidst tons of threads, we see two that are referencing ```org.tmatesoft.svn.core.internal.util.jna```: ```pool-1-thread-2 for channel "pool-1-thread-2 for channel" Id=16 Group=main RUNNABLE at com.sun.jna.Native.initIDs(Native Method) at com.sun.jna.Native.(Native.java:148) at org.tmatesoft.svn.core.internal.util.jna.JNALibraryLoader.(JNALibraryLoader.java:50) at org.tmatesoft.svn.core.internal.util.jna.SVNWin32Util.getApplicationDataPath(SVNWin32Util.java:113) at org.tmatesoft.svn.core.internal.util.jna.SVNJNAUtil.getApplicationDataPath(SVNJNAUtil.java:196) at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.getApplicationDataPath(SVNFileUtil.java:1948) at org.tmatesoft.svn.core.wc.SVNWCUtil.getDefaultConfigurationDirectory(SVNWCUtil.java:57) at hudson.scm.SubversionSCM.createSvnAuthenticationManager(SubversionSCM.java:1055) at hudson.scm.SubversionSCM.createClientManager(SubversionSCM.java:1032) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:965) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:945) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2719) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Number of locked synchronizers = 1 java.util.concurrent.ThreadPoolExecutor$Worker@5f599d56 ``` ``` pool-1-thread-916 for channel "pool-1-thread-916 for channel" Id=930 Group=main RUNNABLE at org.tmatesoft.svn.core.internal.util.jna.SVNWin32Util.getApplicationDataPath(SVNWin32Util.java:113) at org.tmatesoft.svn.core.internal.util.jna.SVNJNAUtil.getApplicationDataPath(SVNJNAUtil.java:196) at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.getApplicationDataPath(SVNFileUtil.java:1948) at org.tmatesoft.svn.core.wc.SVNWCUtil.getDefaultConfigurationDirectory(SVNWCUtil.java:57) at hudson.scm.SubversionSCM.createSvnAuthenticationManager(SubversionSCM.java:1055) at hudson.scm.SubversionSCM.createClientManager(SubversionSCM.java:1032) at hudson.scm.Subv
[JIRA] [subversion-plugin] (JENKINS-3276) Wrong username used for login to SVN
Title: Message Title Dorian Daumiller commented on JENKINS-3276 Re: Wrong username used for login to SVN Stefan Brausch: Thank you sir, your comment made me look on my server and find an old SVN command line credentials cache, which had led to inexplicable log entries on my SVN server about invalid credentials whenever somebody as much as changed an SVN URL. [Tue Mar 15 13:57:01.547853 2016] [authnz_sspi:error] [pid 123:tid 123] (OS 1326)The user name or password is incorrect. : [client 10.42.28.135:56622] user \\: authentication failure for "/svn/" After your comment on finding the user that starts Jenkins I made the discovery that, on Windows, there is an additional user "local SystemUser" whose AppData directory is not at c:\users\\AppData, but at c:\windows\system32\config\systemprofile\AppData. This was happening only on our Legacy Jenkins (which uses tremendously outdated versions of everything), but upgrading to Credentials Plugin V2.1 did not fix this (hat tip to stephenconnolly). 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.
