[JIRA] (JENKINS-51750) Config file provider doesn't always copy file to pipeline
Title: Message Title Dominik Bartholdi closed an issue as Duplicate Jenkins / JENKINS-51750 Config file provider doesn't always copy file to pipeline Change By: Dominik Bartholdi Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53422) Declarative pipeline: stdin/stdout/stderr of a remote process are not redirected
Title: Message Title Yuxiang Zhu created an issue Jenkins / JENKINS-53422 Declarative pipeline: stdin/stdout/stderr of a remote process are not redirected Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-09-05 04:33 Priority: Major Reporter: Yuxiang Zhu When running a build step in a declarative pipeline, remote processes started by Launcher doesn't redirect their stdin/stdout/stderr. This breaks many plugins which run remote processes on a slave: Proc proc = launcher.launch().cmds(commands).pwd(filePath).readStdout().readStderr().start(); InputStream stdout = proc.getStdout(); // stdout is null InputStream stderr = proc.getStderr(); // stderr is null This happens because Kubernetes plugin wraps the steps with a `container` statement, which uses ContainerExecDecorator to run remote commands via the Kubernetes exec API rather than the Jenkins agent. From my understanding, this is used to implement the `container` statement in the DSL, which can run a command in a sidecar container. Considering the feature of running command in a sidecar container is still marked as `ALPHA` in the document, there are still some compatibility issues like: 1. Forwarding streams between stdin/stdout/stderr of a remote process and master is currently not supported. 2. Environment variables and effective UID/GID are not inherited from the JNLP process. 3. The process started with Kubernetes exec API always has a parent PID 0. I would like to change the process of translating declarative pipeline code: Unless the pipeline user specifies an alternative default container to run pipeline steps, the pipeline steps will not be enclosed with a `container`
[JIRA] (JENKINS-53402) Connection to ALM Octane server failed
Title: Message Title Daniel Gront assigned an issue to Michael Seldin Jenkins / JENKINS-53402 Connection to ALM Octane server failed Change By: Daniel Gront Assignee: Daniel Gront Michael Seldin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53402) Connection to ALM Octane server failed
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53402 Connection to ALM Octane server failed Change By: Daniel Gront Labels: jenkins octane Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53421) Multibranch Declarative Pipeline No such property: pipeline
Title: Message Title Dean Smith commented on JENKINS-53421 Re: Multibranch Declarative Pipeline No such property: pipeline William Brawner did you also update your plugins? I just had the same issue and tracked the cause down to updating the Script Security plugin from 1.44 to 1.45, rather than the latest Jenkins update (I also did 2.140 to 2.141). You can go to Plugin Manage > Installed, find the Script Security plugin and then the 'Downgrade to 1.44' button and you should then be good after a restart. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53421) Multibranch Declarative Pipeline No such property: pipeline
Title: Message Title
William Brawner updated an issue
Jenkins / JENKINS-53421
Multibranch Declarative Pipeline No such property: pipeline
Change By:
William Brawner
Hi Jenkins devs, I had a few projects set up as Multibranch Pipeline Projects and they worked great up until I updated this afternoon. Since then, all of my previously working pipelines have broken, and I'm getting this error message on all of them: groovy.lang.MissingPrope {code:java}groovy.lang.MissingPropertyException: No such property: pipeline for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:130) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:1) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)
[JIRA] (JENKINS-53421) Multibranch Declarative Pipeline No such property: pipeline
Title: Message Title
William Brawner updated an issue
Jenkins / JENKINS-53421
Multibranch Declarative Pipeline No such property: pipeline
Change By:
William Brawner
Hi Jenkins devs, I had a few projects set up as Multibranch Pipeline Projects and they worked great up until I updated this afternoon. Since then, all of my previously working pipelines have broken, and I'm getting this error message on all of them: groovy.lang.MissingPrope { {{{ code:java} groovy.lang.MissingPropertyException: No such property: pipeline for class: groovy.lang.Binding {{ \{{ at groovy.lang.Binding.getVariable(Binding.java:63) {{ \{{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:130) {{ \{{ at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) {{ \{{ at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) {{ \{{ at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) {{ \{{ at WorkflowScript.run(WorkflowScript:1) {{ {{ at ___cps.transform___(Native Method) {{ \{{ at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) {{ \{{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) {{ \{{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) {{ \{{ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) {{ \{{ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) {{ \{{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) {{ \{{ at java.lang.reflect.Method.invoke(Method.java:498) {{ \{{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) {{ \{{ at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46) {{ \{{ at com.cloudbees.groovy.cps.Next.step(Next.java:83) {{ \{{ at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) {{ \{{ at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) {{ \{{ at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) {{ \{{ at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) {{ \{{ at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) {{ \{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34) {{ \{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59) {{ \{{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) {{ \{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58) {{ \{{ at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174) {{ \{{
[JIRA] (JENKINS-53421) Multibranch Declarative Pipeline No such property: pipeline
Title: Message Title
William Brawner updated an issue
Jenkins / JENKINS-53421
Multibranch Declarative Pipeline No such property: pipeline
Change By:
William Brawner
Hi Jenkins devs, I had a few projects set up as Multibranch Pipeline Projects and they worked great up until I updated this afternoon. Since then, all of my previously working pipelines have broken, and I'm getting this error message on all of them: {{ {{ groovy.lang.MissingPropertyException: No such property: pipeline for class: groovy.lang.Binding}} }} {{ \{{ at groovy.lang.Binding.getVariable(Binding.java:63)}} }} {{ \{{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:130)}} }} {{ \{{ at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)}} }} {{ \{{ at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)}} }} {{ \{{ at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)}} }} {{ \{{ at WorkflowScript.run(WorkflowScript:1)}} }} {{ {{ at ___cps.transform___(Native Method)}} }} {{ \{{ at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)}} }} {{ \{{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)}} }} {{ \{{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)}} }} {{ \{{ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)}} }} {{ \{{ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)}} }} {{ \{{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}} }} {{ \{{ at java.lang.reflect.Method.invoke(Method.java:498)}} }} {{ \{{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)}} }} {{ \{{ at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46)}} }} {{ \{{ at com.cloudbees.groovy.cps.Next.step(Next.java:83)}} }} {{ \{{ at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)}} }} {{ \{{ at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)}} }} {{ \{{ at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)}} }} {{ \{{ at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)}} }} {{ \{{ at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)}} }} {{ \{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)}} }} {{ \{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)}} }} {{ \{{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)}} }} {{ \{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)}} }} {{ \{{ at
[JIRA] (JENKINS-53421) Multibranch Declarative Pipeline No such property: pipeline
Title: Message Title
William Brawner updated an issue
Jenkins / JENKINS-53421
Multibranch Declarative Pipeline No such property: pipeline
Change By:
William Brawner
Hi Jenkins devs, I had a few projects set up as Multibranch Pipeline Projects and they worked great up until I updated this afternoon. Since then, all of my previously working pipelines have broken, and I'm getting this error message on all of them: {{ groovy.lang.MissingPropertyException: No such property: pipeline for class: groovy.lang.Binding}}{{ at groovy.lang.Binding.getVariable(Binding.java:63)}}{{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:130)}}{{ at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)}}{{ at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)}}{{ at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)}}{{ at WorkflowScript.run(WorkflowScript:1)}}{{ at ___cps.transform___(Native Method)}}{{ at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)}}{{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)}}{{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)}}{{ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)}}{{ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)}}{{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}}{{ at java.lang.reflect.Method.invoke(Method.java:498)}}{{ at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)}}{{ at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46)}}{{ at com.cloudbees.groovy.cps.Next.step(Next.java:83)}}{{ at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)}}{{ at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)}}{{ at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)}}{{ at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)}}{{ at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)}}{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)}}{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)}}{{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)}}{{ at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)}}{{ at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)}}{{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)}}{{ at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)}}{{ at
[JIRA] (JENKINS-53421) Multibranch Declarative Pipeline No such property: pipeline
Title: Message Title
William Brawner created an issue
Jenkins / JENKINS-53421
Multibranch Declarative Pipeline No such property: pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-09-05 02:31
Environment:
Jenkins 2.141 Pipeline 2.5 Pipeline Declarative 1.3.1 Pipeline Groovy 2.54
Priority:
Blocker
Reporter:
William Brawner
Hi Jenkins devs, I had a few projects set up as Multibranch Pipeline Projects and they worked great up until I updated this afternoon. Since then, all of my previously working pipelines have broken, and I'm getting this error message on all of them: groovy.lang.MissingPropertyException: No such property: pipeline for class: groovy.lang.Binding {{ at groovy.lang.Binding.getVariable(Binding.java:63)}} {{ at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:130)}} {{ at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)}} {{ at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)}} {{ at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)}} {{ at WorkflowScript.run(WorkflowScript:1)}} {{ at __cps.transform__(Native Method)}} {{ at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)}} {{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)}} {{ at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)}} {{ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)}} {{ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)}} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}} {{ at
[JIRA] (JENKINS-33979) github-organization-folder-plugin checks out code using HTTPS and not SSH
Title: Message Title Asaf Peleg commented on JENKINS-33979 Re: github-organization-folder-plugin checks out code using HTTPS and not SSH Thanks Jesse Glick I was able to find checkout over SSH but we're still contending with the github api quota and our jobs are just getting stuck before they start when we hit the quota. I started a discussion in the Jenkins User group to see if anyone can help. https://groups.google.com/d/msgid/jenkinsci-users/7a6d7ef8-1700-4042-941b-d1ba74fef440%40googlegroups.com?utm_medium=email_source=footer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46120) OOM: MultiJob and adding value to end of environment variable, eg. path
Title: Message Title Luke Chen updated an issue Jenkins / JENKINS-46120 OOM: MultiJob and adding value to end of environment variable, eg. path Change By: Luke Chen Comment: [~yorammi] could you kindly provide more details of the "tikal-multijob-plugin issues cleanup" work. I don't think the "*multijob*" failure was addressed in this ticket. I started to see Multijob failures (due to java heap OOM) since after a recent plugin upgrade (multijob v1.31, env injector v2.1.6) in my Jenkins system. Downgrading (multijob v1.29, env injector v2.1.5) did not seem to help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53355) use credential storage for Jira Pipeline Steps authentication
Title: Message Title Naresh Rayapati edited a comment on JENKINS-53355 Re: use credential storage for Jira Pipeline Steps authentication Thanks for reporting this [~jacurt], we already have another Jira logged to implement something similar https://issues.jenkins-ci.org/browse/ JENKINS-47199 I will look into this soon, but please don't mind to issue a pull request when you have a moment. Thanks again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53355) use credential storage for Jira Pipeline Steps authentication
Title: Message Title Naresh Rayapati commented on JENKINS-53355 Re: use credential storage for Jira Pipeline Steps authentication Thanks for reporting this Jason Curtis, we already have another Jira logged to implement something similar https://issues.jenkins-ci.org/browse/JENKINS-47199 I will look into this soon, but please don't mind to issue a pull request when you have a moment. Thanks again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53361) Copy files using a regular expresion
Title: Message Title Naresh Rayapati commented on JENKINS-53361 Re: Copy files using a regular expresion +1, Thanks for logging this Sergio Merino. Nice to have feature. I will look into it soon, please don't mind to issue a pull request if you have already some ideas around this. And also we can achieve this by running a script to create a temp directory with filter and just copy that directory over instead, but yeah it is a bit of hacky. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Gavin Mogan commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding HA~ its so obvious after the fact eh. Its pretty easy to roll back to a previous version, and hopefully if anyone else gets this bug they'll see this issue, so I think it can easily wait for abit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Andrew Bayer commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Ugh I see exactly what I did wrong, too. Sorry for the inconvenience. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Andrew Bayer commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Likely due to https://github.com/jenkinsci/script-security-plugin/commit/6d1e02606d0803eb1445bd96b8f0ba342abb2864 - sigh. I missed something. I’ll get it fixed ASAP tomorrow morning. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46120) OOM: MultiJob and adding value to end of environment variable, eg. path
Title: Message Title Luke Chen commented on JENKINS-46120 Re: OOM: MultiJob and adding value to end of environment variable, eg. path Yoram Michaeli could you kindly provide more details of the "tikal-multijob-plugin issues cleanup" work. I don't think the "multijob" failure was addressed in this ticket. I started to see Multijob failures (due to java heap OOM) since after a recent plugin upgrade (multijob v1.31, env injector v2.1.6) in my Jenkins system. Downgrading (multijob v1.29, env injector v2.1.5) did not seem to help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53420 groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Well, that’s not good at all. I’ll dig into this first thing tomorrow. Change By: Andrew Bayer Issue Type: Improvement Bug Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Gavin Mogan commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Switching to http://archives.jenkins-ci.org/plugins/script-security/1.44/script-security.hpi made the script run again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Gavin Mogan created an issue Jenkins / JENKINS-53420 groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Issue Type: Improvement Assignee: Andrew Bayer Components: script-security-plugin Created: 2018-09-04 23:45 Environment: Plugin Listace-editor 1.1 true ansicolor 0.5.2 true apache-httpcomponents-client-4-api 4.5.5-3.0 true authentication-tokens 1.3 true aws-credentials 1.23 true aws-java-sdk 1.11.341 true azure-app-service 0.3.1 true azure-commons 0.2.6 true azure-credentials 1.6.0 true blueocean 1.8.2 true blueocean-autofavorite 1.2.2 true blueocean-bitbucket-pipeline 1.8.2 true blueocean-commons 1.8.2 true blueocean-config 1.8.2 true blueocean-core-js 1.8.2 true blueocean-dashboard 1.8.2 true blueocean-display-url 2.2.0 true blueocean-events 1.8.2 true blueocean-git-pipeline 1.8.2 true blueocean-github-pipeline 1.8.2 true blueocean-i18n 1.8.2 true blueocean-jira 1.8.2 true blueocean-jwt 1.8.2 true blueocean-personalization 1.8.2 true blueocean-pipeline-api-impl 1.8.2 true blueocean-pipeline-editor 1.8.2 true blueocean-pipeline-scm-api 1.8.2 true blueocean-rest 1.8.2 true blueocean-rest-impl 1.8.2 true blueocean-web 1.8.2 true bouncycastle-api 2.17 true branch-api 2.0.20 true cloudbees-bitbucket-branch-source 2.2.12 true cloudbees-folder 6.5.1 true command-launcher 1.2 true credentials 2.1.18 true credentials-binding 1.16 true display-url-api 2.2.0 true docker-build-publish 1.3.2 true docker-build-step 2.0 true docker-commons 1.13 true docker-java-api 3.0.14 true docker-plugin 1.1.5 true docker-workflow 1.17 true durable-task 1.25 true ec2 1.39 true email-ext 2.63 true favorite 2.3.2 true git 3.9.1 true git-client 2.7.3 true git-server 1.7 true github 1.29.2 true github-api 1.92 true github-autostatus 3.0.1 true github-branch-source 2.3.6 true github-oauth 0.29 true github-pr-comment-build 2.0 true github-pr-coverage-status 1.10.0 true github-pullrequest 0.2.3 true greenballs 1.15 true handlebars 1.1.1 true handy-uri-templates-2-api 2.1.6-1.0 true html5-notifier-plugin 1.5 true htmlpublisher 1.16 true http_request 1.8.22 true icon-shim 2.0.3 true jackson2-api 2.8.11.3 true javadoc 1.4 true jdk-tool 1.1 true jenkins-design-language 1.8.2 true jira 3.0.1 true jquery-detached 1.2.1 true jsch 0.1.54.2 true junit 1.24 true mailer 1.21 true matrix-auth 2.3 true matrix-project 1.13 true maven-plugin 3.1.2 true mercurial 2.4 true momentjs 1.1.1 true node-iterator-api 1.5.0 true nunit 0.23 true pipeline-build-step 2.7 true pipeline-graph-analysis 1.7 true
[JIRA] (JENKINS-53397) ChannelClosedException when using kafka nodes
Title: Message Title Federico Naum commented on JENKINS-53397 Re: ChannelClosedException when using kafka nodes Disregard my last comment, I just saw Oleg Nenashev comments on the PR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53397) ChannelClosedException when using kafka nodes
Title: Message Title Federico Naum commented on JENKINS-53397 Re: ChannelClosedException when using kafka nodes Hi Pham Vu Tuan, thanks for the quick turn around. I do not know much about jenkins/remoting dependencies, but I noticed in your PR that you have jenkins.version=2.129 , and the remoting version 3.26 is only bundled on Jenkins 2.141 (https://jenkins.io/changelog/) Shouldn't this need to be updated as well? F Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43578) Declarative pipeline: post section doesn't play nice with agent none
Title: Message Title
Kevin Fox commented on JENKINS-43578
Re: Declarative pipeline: post section doesn't play nice with agent none
This looks like it does the trick: post { always { node('docker') { script { docker.image("kfox/kubeclient:2018-08-29-1").inside {
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitSCM checkout returns same values on second different call
Title: Message Title Mark Waite edited a comment on JENKINS-53346 Re: GitSCM checkout returns same values on second different call I've confirmed that the bug exists as reported. The map returned by the second checkout has the same values as the map returned by the first checkout.Refer to the [Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-53346/Jenkinsfile] in my [JENKINS-53346 test branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-53346/ README.md ] for an alternative to obtain the same information using a shell call. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43578) Declarative pipeline: post section doesn't play nice with agent none
Title: Message Title
Kevin Fox commented on JENKINS-43578
Re: Declarative pipeline: post section doesn't play nice with agent none
tried with step and without. something like: post { always { node('docker') { docker.image("kfox/kubeclient:2018-08-29-1").inside { sh 'ls /' WorkflowScript: 62: Expected a symbol @ line 62, column 17. docker.image("kfox/kubeclient:2018-08-29-1").inside { Not liking something there.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitSCM checkout returns same values on second different call
Title: Message Title Mark Waite edited a comment on JENKINS-53346 Re: GitSCM checkout returns same values on second different call When I look at [GitSCM#buildEnvironment(Run, Map)|https://github.com/jenkinsci/git-plugin/blob/556bb5aa77035d51f99d8813cc95ceff3f163736/src/main/java/hudson/plugins/git/GitSCM.java#L1343] it appears to compute the value for GIT_BRANCH, GIT_LOCAL_BRANCH, GIT_CHECKOUT_DIR, and GIT_COMMIT from build data and last built revision of the workspace.The GIT_PREVIOUS_COMMIT, GIT_PREVIOUS_SUCCESSFUL_COMMIT, and GIT_URL are based on the current conditions of the repository.However, if the call to buildEnvironment happens before build data is updated for the running build, or if getBuildData(build) returns the same Revision (line 1344) even though there are two different build data values for the checkout, then that may indicate the problem is inside the git plugin and only related to workflow-scm-step because that is what shows the bug in GitSCM. I confess, I'd need a debugger and some test cases before I could be confident where the bug lies. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitSCM checkout returns same values on second different call
Title: Message Title Mark Waite commented on JENKINS-53346 Re: GitSCM checkout returns same values on second different call When I look at GitSCM#buildEnvironment(Run, Map) it appears to compute the value for GIT_BRANCH, GIT_LOCAL_BRANCH, GIT_CHECKOUT_DIR, and GIT_COMMIT from build data and last built revision of the workspace. The GIT_PREVIOUS_COMMIT, GIT_PREVIOUS_SUCCESSFUL_COMMIT, and GIT_URL based on the current conditions of the repository. However, if the call to buildEnvironment happens before build data is updated for the running build, or if getBuildData(build) returns the same Revision (line 1344) even though there are two different build data values for the checkout, then that may indicate the problem is inside the git plugin and only related to workflow-scm-step because that is what shows the bug in GitSCM. I confess, I'd need a debugger and some test cases before I could be confident where the bug lies. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33979) github-organization-folder-plugin checks out code using HTTPS and not SSH
Title: Message Title Jesse Glick commented on JENKINS-33979 Re: github-organization-folder-plugin checks out code using HTTPS and not SSH IIRC the UI is now in a Behaviors dropdown. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43578) Declarative pipeline: post section doesn't play nice with agent none
Title: Message Title
Sean Talts edited a comment on JENKINS-43578
Re: Declarative pipeline: post section doesn't play nice with agent none
Maybe the scripted pipeline version would work, something like {code:java} node {/* Requires the Docker Pipeline plugin to be installed */docker.image('node:7-alpine').inside {stage('Test') \ { sh 'node --version' }} } {code} from pressing "Toggle scripted pipeline (Advanced)" on this page: [ https://jenkins.io/doc/book/pipeline/docker/ ]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43578) Declarative pipeline: post section doesn't play nice with agent none
Title: Message Title
Sean Talts commented on JENKINS-43578
Re: Declarative pipeline: post section doesn't play nice with agent none
Maybe the scripted pipeline version would work, something like node { /* Requires the Docker Pipeline plugin to be installed */ docker.image('node:7-alpine').inside { stage('Test') \{ sh 'node --version' } } } from pressing "Toggle scripted pipeline (Advanced)" on this page: https://jenkins.io/doc/book/pipeline/docker/
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43578) Declarative pipeline: post section doesn't play nice with agent none
Title: Message Title Kevin Fox commented on JENKINS-43578 Re: Declarative pipeline: post section doesn't play nice with agent none Interesting. How do you specify an agent section so that you can run it within a container on the node? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) Downstream pipeline no longer triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: Downstream pipeline no longer triggered Tested with 3.5.12-beta-4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23283) nested view plugin get list of jobs in a sub view ?
Title: Message Title Chris Neal commented on JENKINS-23283 Re: nested view plugin get list of jobs in a sub view ? Hi! I am trying to get these scripts to work. The problem is that I have "folders" between my views. And since I don't know what the expected output is, or where the hudson function starts, I can't get any output other than "null" as a response. Can somoene point me to the place where the expected output is described? Thanks, -Chris Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43578) Declarative pipeline: post section doesn't play nice with agent none
Title: Message Title Sean Talts commented on JENKINS-43578 Re: Declarative pipeline: post section doesn't play nice with agent none Kevin, The `node` function appears to work in the `post` section, so this is what we do for now: https://github.com/stan-dev/math/blob/18755752b563221cadeb39d4ce092c4c226e26ae/Jenkinsfile#L252 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43578) Declarative pipeline: post section doesn't play nice with agent none
Title: Message Title Kevin Fox commented on JENKINS-43578 Re: Declarative pipeline: post section doesn't play nice with agent none Has there been a solution for this found yet? I want to run agent none so I can run different docker containers per test. But I want to have a post always job that runs in a kubernetes client docker image that cleans out the cluster of anything created by any of the stages. I haven't been able to figure out a way to do this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Elliot Babchick edited a comment on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion Thanks! I'm also working on getting a support bundle while the issue is reproduced, but unfortunately while the issue is occurring Jenkins ' tends to be in a very large backlogged state w.r.t the build queue, and attempting to generate the bundle crashes Jenkins with an OOM :( We'll keep trying ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title Jesse Glick commented on JENKINS-40839 Re: pipeline timeout doesn't kill the job Amir Barkal that case is perhaps a duplicate of JENKINS-28822. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Elliot Babchick commented on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion Thanks! I'm also working on getting a support bundle while the issue is reproduced, but unfortunately while the issue is occurring Jenkins' tends to be in a very large backlogged state w.r.t the build queue, and attempting to generate the bundle crashes Jenkins with an OOM We'll keep trying ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title Jesse Glick commented on JENKINS-28822 Re: Can't distinguish between durable task abort and failure in workflow plugin Joerg Schwaerzler that is indeed related, but should have been fixed by this in 2.21 AFAIK. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title John Hall commented on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option I get the same issue randomly when Gerrit triggers a build. org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 97: Invalid option type "timeout". Valid option types: [authorizationMatrix, buildDiscarder, catchError, checkoutToSubdirectory, disableConcurrentBuilds, disableResume, durabilityHint, office365ConnectorWebhooks, overrideIndexTriggers, preserveStashes, retry, script, skipDefaultCheckout, skipStagesAfterUnstable, timestamps, waitUntil, withContext, withCredentials, withEnv, ws] @ line 97, column 9. timeout(time: maxBuildTimeinMinutes, unit: 'MINUTES') ^ 1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:131) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:125) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:330) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-39598) MultiSCM/config.jelly passes descriptors=null
Title: Message Title Jesse Glick commented on JENKINS-39598 Re: MultiSCM/config.jelly passes descriptors=null Jakub Pawlinski huh? multiple-scms has no dep on mercurial. mercurial has a dep on multiple-scms, but it is optional, so multiple-scms can be disabled. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title Igor Solovko commented on JENKINS-52923 Re: Error Signal Description not displayed in Blue Ocean similar 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53224) [P4 Plugin] Always allow polling to occur
Title: Message Title Kurt Routley assigned an issue to Paul Allen Jenkins / JENKINS-53224 [P4 Plugin] Always allow polling to occur Change By: Kurt Routley Assignee: Kurt Routley Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53224) [P4 Plugin] Always allow polling to occur
Title: Message Title Kurt Routley updated an issue Jenkins / JENKINS-53224 [P4 Plugin] Always allow polling to occur Change By: Kurt Routley P4 Plugin currently will not start polling if the job is building or if concurrent builds are disabled. This prevents builds from being able to queue up, and creates a quiet period of at least the polling interval. This prevents the "continuous" part of continuous integration, need to remove this check to always allow polling to occur. Jobs configurations themselves can handle concurrency checks. I am working on the merge request EDIT: pull request created here: https://github.com/jenkinsci/p4-plugin/pull/79 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-53223 Finished pipeline jobs appear to occupy executor slots long after completion Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53223) Finished pipeline jobs appear to occupy executor slots long after completion
Title: Message Title Devin Nusbaum commented on JENKINS-53223 Re: Finished pipeline jobs appear to occupy executor slots long after completion Maybe a dupe of JENKINS-45571 and/or JENKINS-51568? Thanks for including the thread dumps Elliot Babchick, I will take a look and see if anything gives us an idea of the cause. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Andrew Bayer commented on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 FYI, 3.0 has been removed from the update center. I've had multiple reports that downgrading config-files-provider to 2.18 fixes all symptoms those reports encountered (including folder permissions and shared libraries being broken), so that's a clear path forward for now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53302) Pipeline script from SCM: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods round, org.codehaus.groovy.runtime.DefaultGroovyMethods toF
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53302 Pipeline script from SCM: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods round, org.codehaus.groovy.runtime.DefaultGroovyMethods toFloat Change By: Andrew Bayer Component/s: script-security-plugin Component/s: pipeline Component/s: pipeline-build-step-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53253) Rename "Jenkinsfile" to ".jenkins"
Title: Message Title Andrew Bayer closed an issue as Won't Fix We've already got too much tooling that expects it to be named Jenkinsfile and too many existing uses of Jenkinsfile out in the wild to rename it at this point. Sorry. Jenkins / JENKINS-53253 Rename "Jenkinsfile" to ".jenkins" Change By: Andrew Bayer Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53246) Regression in pipeline job features.
Title: Message Title Andrew Bayer assigned an issue to Unassigned Jenkins / JENKINS-53246 Regression in pipeline job features. Change By: Andrew Bayer Assignee: Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53283) Unable to use WorkflowScript multiple times in libraries class constructor
Title: Message Title
Andrew Bayer commented on JENKINS-53283
Re: Unable to use WorkflowScript multiple times in libraries class constructor
I honestly can't remember seeing that lib.Foo.new syntax before. Just for giggles, does it work if you just do
library("Common@${env.LIB_VERSION}")
def fooLib = new com.mycompany.jenkins.Foo(this)
def barLib = new com.mycompany.jenkins.Bar(this)
def stuffLib = new com.mycompany.jenkins.Stuff(this)
Or, for that matter, if you instantiate the same class multiple times?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitSCM checkout returns same values on second different call
Title: Message Title Andrew Bayer commented on JENKINS-53346 Re: GitSCM checkout returns same values on second different call Mark Waite - if I'm remembering the code correctly, this would mean that GitSCM#buildEnvironment(Run,Map) is populating the map passed to it with the same values every time it's called - is that right? If so, I should remove workflow-scm-step-plugin from the components, since we're just calling SCM#buildEnvironment(Run,Map) and trusting it to populate the map with the right things. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitSCM checkout returns same values on second different call
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53346 GitSCM checkout returns same values on second different call Change By: Andrew Bayer Component/s: workflow-scm-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53374) file permissions are lost after unstashing on windows node
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53374 file permissions are lost after unstashing on windows node Change By: Andrew Bayer Component/s: workflow-basic-steps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53403) Stage view overlaps right hand side graphis making them unclickable.
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53403 Stage view overlaps right hand side graphis making them unclickable. Change By: Andrew Bayer Component/s: pipeline-stage-view-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53406) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Title: Message Title Andrew Bayer commented on JENKINS-53406 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: What's your question? You've got a compilation error in the script you're loading. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53222) [P4 Plugin] Add Full Set of FileAction Enum Types to P4AffectedFile
Title: Message Title Kurt Routley assigned an issue to Paul Allen Jenkins / JENKINS-53222 [P4 Plugin] Add Full Set of FileAction Enum Types to P4AffectedFile Change By: Kurt Routley Assignee: Kurt Routley Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53222) [P4 Plugin] Add Full Set of FileAction Enum Types to P4AffectedFile
Title: Message Title Kurt Routley updated an issue Jenkins / JENKINS-53222 [P4 Plugin] Add Full Set of FileAction Enum Types to P4AffectedFile Change By: Kurt Routley P4Affected file currently only contains a subset of the possible object types from FileAction. Include the full set of FileAction enum types in P4AffectedFile with EditType descriptions for each. I am working on a merge request for this. EDIT: Created Pull Request: https://github.com/jenkinsci/p4-plugin/pull/78 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53222) [P4 Plugin] Add Full Set of FileAction Enum Types to P4AffectedFile
Title: Message Title Kurt Routley commented on JENKINS-53222 Re: [P4 Plugin] Add Full Set of FileAction Enum Types to P4AffectedFile Created Pull Request: https://github.com/jenkinsci/p4-plugin/pull/78 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53221) [P4 Plugin] Add P4_ROOT to injected environment variables
Title: Message Title Kurt Routley assigned an issue to Paul Allen Jenkins / JENKINS-53221 [P4 Plugin] Add P4_ROOT to injected environment variables Change By: Kurt Routley Assignee: Kurt Routley Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53221) [P4 Plugin] Add P4_ROOT to injected environment variables
Title: Message Title Kurt Routley updated an issue Jenkins / JENKINS-53221 [P4 Plugin] Add P4_ROOT to injected environment variables Change By: Kurt Routley The P4 Plugin does not inject the P4_ROOT environment variable. It is nice to have access to this, as often the p4 sync location can be different from the current workspace.I have a merge request incoming for this. EDIT: Pull request created at https://github.com/jenkinsci/p4-plugin/pull/77 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53221) [P4 Plugin] Add P4_ROOT to injected environment variables
Title: Message Title Kurt Routley commented on JENKINS-53221 Re: [P4 Plugin] Add P4_ROOT to injected environment variables ... redoing pull request to proper branch: https://github.com/jenkinsci/p4-plugin/pull/77 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Pablo Ramirez commented on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException I've patched kubernetes-1.12.4 tag with JENKINS-53370 branch and I still having the same error. Should I use master (1.12.5-SNAPSHOT) patched? Sep 04, 2018 4:55:38 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision WARNING: Failed to count the # of live instances on Kubernetes java.lang.NullPointerException at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:504) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:447) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53221) [P4 Plugin] Add P4_ROOT to injected environment variables
Title: Message Title Kurt Routley commented on JENKINS-53221 Re: [P4 Plugin] Add P4_ROOT to injected environment variables Created pull request here: https://github.com/p4paul/p4-jenkins/pull/39 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53221) [P4 Plugin] Add P4_ROOT to injected environment variables
Title: Message Title Kurt Routley commented on JENKINS-53221 Re: [P4 Plugin] Add P4_ROOT to injected environment variables Adding P4_Root to environment variable. Submitted to personal forked repo at https://github.com/kroutley/p4-plugin-1/commit/a1b0aa6742b1529764f015257d58f136004d610b Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 hmm, oh damn seems the easiest looking change of all broke the whole thing... and yes sure the idea never was to have the comparator beeing serialized into the config... anyway, [~abayer] and [~oleg_nenashev] many thanks for the quick reaction, I will need to check how I can fix this without lifting the 'compatibleSince' sorry to everyone I caused issues with this Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Dominik Bartholdi commented on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 hmm, oh damn seems the easiest looking change of all broke the whole thing... and yes sure the idea never was to have the comparator beeing serialized into the config... anyway, Andrew Bayer and Oleg Nenashev many thanks for the quick reaction, I will need to check how I can fix this without lifting the 'compatibleSince' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Hector Santana commented on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 org.jenkinsci.plugins.configfiles.GlobalConfigFiles Managed files ConversionException: org.jenkinsci.plugins.configfiles.GlobalConfigFiles$1 : org.jenkinsci.plugins.configfiles.GlobalConfigFiles$1 Debugging information message : org.jenkinsci.plugins.configfiles.GlobalConfigFiles$1 cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message : org.jenkinsci.plugins.configfiles.GlobalConfigFiles$1 class : java.util.TreeSet required-type : java.util.TreeSet converter-type : com.thoughtworks.xstream.converters.collections.TreeSetConverter path : /org.jenkinsci.plugins.configfiles.GlobalConfigFiles/configs/comparator line number : 4 ---, MissingFieldException: No field 'org.jenkinsci.plugins.configfiles.xml.XmlConfig' found in class 'org.jenkinsci.plugins.configfiles.GlobalConfigFiles', MissingFieldException: No field 'org.jenkinsci.plugins.managedscripts.PowerShellConfig' found in class 'org.jenkinsci.plugins.configfiles.GlobalConfigFiles', MissingFieldException: No field 'org.jenkinsci.plugins.managedscripts.PowerShellConfig' found in class 'org.jenkinsci.plugins.configfiles.GlobalConfigFiles', MissingFieldException: No field 'org.jenkinsci.plugins.managedscripts.PowerShellConfig' found in class 'org.jenkinsci.plugins.configfiles.GlobalConfigFiles' We also had the same problem when updated from 2.18 to 3.0 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
[JIRA] (JENKINS-53419) Demo Jenkins Evergreen successfully at DevOps World Jenkins World in SF
Title: Message Title Oleg Nenashev commented on JENKINS-53419 Re: Demo Jenkins Evergreen successfully at DevOps World Jenkins World in SF I especially like *successfully* in the summary Looking forward to see the demo! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53312) Scheduled builds for Pipeline jobs don't appear in Calendar View
Title: Message Title Sven Schoenung resolved as Fixed Jenkins / JENKINS-53312 Scheduled builds for Pipeline jobs don't appear in Calendar View Change By: Sven Schoenung Status: Open Resolved Resolution: Fixed Released As: 0.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53312) Scheduled builds for Pipeline jobs don't appear in Calendar View
Title: Message Title
Sven Schoenung commented on JENKINS-53312
Re: Scheduled builds for Pipeline jobs don't appear in Calendar View
Fix in 0.3.1. There's two ways to configure scheduled builds for pipeline jobs: 1. Using the Jenkins UI (as one would for Free Style Jobs) 2. Using triggers:
pipeline {
agent any
triggers {
cron('H */4 * * 1-5')
}
}
Note that in the second case the job has to be executed once for the cron _expression_ to be picked up.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53419) Demo Jenkins Evergreen successfully at DevOps World Jenkins World in SF
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-53419 Demo Jenkins Evergreen successfully at DevOps World Jenkins World in SF Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-04 18:41 Priority: Critical Reporter: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Tomi Pakarinen commented on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 Why comparator is serialized into config file? It is static constant anyway.. https://github.com/jenkinsci/config-file-provider-plugin/commit/2366eaee6980564e59771897274f38d462bb0abc Can it be made transient? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53418) Provide a one-click button to use easily the CloudFormation template for AWS flavor
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53418 Provide a one-click button to use easily the CloudFormation template for AWS flavor Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-04 18:16 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus Currently, we have only a CloudFormation template that one must use the CLI for to use it. It would much more useful that we provide a button directly usable from GitHub that would take one to the AWS ui and provide the necessary parameters for the given template. Add Comment
[JIRA] (JENKINS-53418) Provide a one-click button to use easily the CloudFormation template for AWS flavor
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53418 Provide a one-click button to use easily the CloudFormation template for AWS flavor Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Andrew Bayer commented on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 Opened https://github.com/jenkins-infra/update-center2/pull/236 to remove 3.0 from the update center. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Scott Schreckengaust commented on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 I second Jens Beyer's comment for a compatibility warning prior to upgrade. How to upgrade correctly (Tomi Pakarinen's comment)? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Andrew Bayer commented on JENKINS-53399 Re: Lost all saved managed files after upgrade to 3.0 I've got at least one report of the upgrade breaking shared libraries and per-project permissions on folders as well - Daniel Beck, I think we should be seriously considering removing 3.0 from the update center. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Sebastian Lopez commented on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53399) Lost all saved managed files after upgrade to 3.0
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-53399 Lost all saved managed files after upgrade to 3.0 Change By: Andrew Bayer Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Carlos Sanchez updated JENKINS-53370 Jenkins / JENKINS-53370 Failed to count the # of live instances on Kubernetes - NullPointerException Change By: Carlos Sanchez Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Carlos Sanchez assigned an issue to Carlos Sanchez Jenkins / JENKINS-53370 Failed to count the # of live instances on Kubernetes - NullPointerException Change By: Carlos Sanchez Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Carlos Sanchez started work on JENKINS-53370 Change By: Carlos Sanchez Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Carlos Sanchez edited a comment on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException I have created a PR , https://github.com/jenkinsci/kubernetes-plugin/pull/378 please take a look. But [~slopez] you should upgrade to a newer version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Carlos Sanchez commented on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException I have created a PR, please take a look. But Sebastian Lopez you should upgrade to a newer version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52950) CLI enable-plugin -restart restarts even if no plugins are enabled
Title: Message Title Matt Sicker updated JENKINS-52950 Jenkins / JENKINS-52950 CLI enable-plugin -restart restarts even if no plugins are enabled Change By: Matt Sicker Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.140 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Jon Starbird commented on JENKINS-53336 Re: inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster Andrew, no I would not need that, pass/fail is sufficient. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53397) ChannelClosedException when using kafka nodes
Title: Message Title Pham Vu Tuan commented on JENKINS-53397 Re: ChannelClosedException when using kafka nodes yes, merged the PR https://github.com/jenkinsci/remoting-kafka-plugin/pull/43, I will try to release soon by the end of this week. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53397) ChannelClosedException when using kafka nodes
Title: Message Title Jeff Thompson commented on JENKINS-53397 Re: ChannelClosedException when using kafka nodes As Oleg mentions, upgrading to Remoting 3.26 will probably clear up that log message, "Trying to unexport an object that's already unexported". That's a good first step. There are still probably other issues after that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53416) Update remoting version to 3.26
Title: Message Title Pham Vu Tuan updated JENKINS-53416 Jenkins / JENKINS-53416 Update remoting version to 3.26 Change By: Pham Vu Tuan Status: In Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53416) Update remoting version to 3.26
Title: Message Title Pham Vu Tuan updated JENKINS-53416 Jenkins / JENKINS-53416 Update remoting version to 3.26 Change By: Pham Vu Tuan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Alexey Grigorov commented on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
Same here. I'm running a @NonCPS labeled method in library and if fails with this error randomly in the middle
import jenkins.*
import jenkins.model.*
import hudson.*
import hudson.model.*
/* This method will find all jobs and verify their disk usage.
Then it will remove job runs to fit quota
That will help to save disk space
*/
@NonCPS
def call() {
def maxRunSize = 21474836480 //20Gb
def maxJobSize = 42949672960 //40Gb
Jenkins.instance.getAllItems(hudson.model.Job).each
{
println it
def runs = it.getBuilds()
def job = it
def totalSize = 0
def jobSizeReached = false
runs.each{
def currentRun = it
def currentRunSize = it.getRootDir().directorySize()
println it
println currentRunSize
switch (currentRunSize) {
case {it > maxRunSize} :
currentRun.delete()
println "deleted " + currentRun + " for having size " + it + " over allowed " + maxRunSize
break
case {it + totalSize > maxJobSize || jobSizeReached } :
jobSizeReached = true
currentRun.delete()
println "deleted " + currentRun + " for not fitting total " + job + " jobs size " + (totalSize+currentRunSize) +" to max allowed " + maxJobSize
break
default :
totalSize += currentRunSize
println 'leaving ' + currentRun + ". current total = " + totalSize
break
}
println '--'
}
println '=='
}
}
--
[Pipeline] echo
[Pipeline] End of Pipeline
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1302)
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:275)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadGroupSynchronously(CpsStepContext.java:248)
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadSynchronously(CpsStepContext.java:237)
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:298)
at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:61)
at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:258)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:206)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
at
[JIRA] (JENKINS-53416) Update remoting version to 3.26
Title: Message Title Pham Vu Tuan updated an issue Jenkins / JENKINS-53416 Update remoting version to 3.26 Change By: Pham Vu Tuan Summary: Update remoting version to 3.26 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym edited a comment on JENKINS-52058 Re: Provide report filename as variable to Groovy parser Second problem that is maybe not a problem because I may miss a configuration is that for one parser I have 4 tab : files, categories, types, issues (ok) but for another parser I have only 2 tabs : types and issues. (ko) In first parser, I can click on "files" tab to have summary per file. that is exactly what I want because in my case : one file parsed = one test so I can see a summary of test result. But unfortunately in the parser of test result I don't have the 4 tabs, I have only 2 tabs. What is strange is that if I click on "issues" tab I can see that file information is present and should be used to have a "files" tab displayed. Only category information is not displayed because not provided by the parser. any idea [Edit] there is no problem, it seems that a new tab is added only if different values are found in a column. in my test, there was only one file this is why there is no "files" tab. right ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52877) Implement PingThread in agent
Title: Message Title Pham Vu Tuan updated an issue Jenkins / JENKINS-52877 Implement PingThread in agent Change By: Pham Vu Tuan Labels: plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Pablo Ramirez commented on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException This is from right now Sep 04, 2018 12:48:52 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 Sep 04, 2018 12:48:52 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template: Kubernetes Pod Template Sep 04, 2018 12:48:52 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Sep 04, 2018 12:48:52 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision WARNING: Failed to count the # of live instances on Kubernetes java.lang.NullPointerException at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:493) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:447) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Add Comment
[JIRA] (JENKINS-52542) Multiple Kafka hosts to achieve fault-tolerant communication
Title: Message Title Pham Vu Tuan updated an issue Jenkins / JENKINS-52542 Multiple Kafka hosts to achieve fault-tolerant communication Change By: Pham Vu Tuan Labels: plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52542) Multiple Kafka hosts to achieve fault-tolerant communication
Title: Message Title Pham Vu Tuan updated an issue Jenkins / JENKINS-52542 Multiple Kafka hosts to achieve fault-tolerant communication Change By: Pham Vu Tuan Summary: Nice2have: Multiple Kafka hosts to achieve fault-tolerant communication Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
