[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title Dale King commented on JENKINS-52420 Re: [JEP-200] Can't serialize class but I assume that it is related to instances of "com.google.common.collect.Multimap"... or not. The class itself is permitted in the core: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/security/whitelisted-classes.txt It is related specifically to instances of "com.google.common.collect.ImmutableListMultimap", which does NOT appear in the whitelist 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-52420) [JEP-200] Can't serialize class
Title: Message Title
Dale King edited a comment on JENKINS-52420
Re: [JEP-200] Can't serialize class
It was mentioned that the stack trace was incomplete, if it helps here is a complete one: { { code:java} Error when executing always post condition:java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun at hudson.XmlFile.write(XmlFile.java:200) at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135) at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123) at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41) at ___cps __cps . transform___ 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.GeneratedMethodAccessor372.invoke(Unknown Source) 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
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title
Dale King edited a comment on JENKINS-52420
Re: [JEP-200] Can't serialize class
It was mentioned that the stack trace was incomplete, if it helps here is a complete one: {{ Error when executing always post condition:java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun at hudson.XmlFile.write(XmlFile.java:200) at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135) at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123) at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41) 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.GeneratedMethodAccessor372.invoke(Unknown Source) 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
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title
Dale King edited a comment on JENKINS-52420
Re: [JEP-200] Can't serialize class
It was mentioned that the stack trace was incomplete, if it helps here is a complete one: {{ Error when executing always post condition: }} {{ java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun }} {{ at hudson.XmlFile.write(XmlFile.java:200) }} {{ at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) }} {{ at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) }} {{ at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) }} {{ at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) }} {{ at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) }} {{ at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) }} {{ at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135] ) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.node(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66] ) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123] ) }} {{ at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41] ) }} {{ 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.GeneratedMethodAccessor372.invoke(Unknown Source) }} {{
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title
Dale King edited a comment on JENKINS-52420
Re: [JEP-200] Can't serialize class
It was mentioned that the stack trace was incomplete, if it helps here is a complete one: {{ Error when executing always post condition: }} {{ java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun }} {{ at hudson.XmlFile.write(XmlFile.java:200) }} {{ at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) }} {{ at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) }} {{ at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) }} {{ at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) }} {{ at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) }} {{ at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) }} {{ at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) }} {{ at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) }} {{ at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135] ) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.node(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66] ) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123] ) }} {{ at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) }} {{ at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar: [ file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41 |file:///var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41] ) }} {{ 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.GeneratedMethodAccessor372.invoke(Unknown Source) }} {{
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title Dale King commented on JENKINS-52420 Re: [JEP-200] Can't serialize class It was mentioned that the stack trace was incomplete, if it helps here is a complete one: Error when executing always post condition: java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class org.jenkinsci.plugins.workflow.job.WorkflowRun at hudson.XmlFile.write(XmlFile.java:200) at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1256) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprintAction.addToRun(DockerFingerprintAction.java:145) at org.jenkinsci.plugins.docker.commons.fingerprint.DockerFingerprints.addRunFacet(DockerFingerprints.java:242) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:194) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135) at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123) at dockerBuild.call(/var/jenkins_home/jobs/dsl-small-app/jobs/arc-maturity-events/jobs/build/branches/Perform-PITest-in-Jenkins/builds/5/libs/jenkins-pipeline-library/vars/dockerBuild.groovy:64) at org.jenkinsci.plugins.docker.workflow.Docker.withRegistry(jar:file:/var/jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:41) 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.GeneratedMethodAccessor372.invoke(Unknown Source) 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
[JIRA] [stash-pullrequest-builder-plugin] (JENKINS-29274) Comment log checker does not handle build names with regex special characters
Title: Message Title Dale King commented on JENKINS-29274 Re: Comment log checker does not handle build names with regex special characters I reopened the issue I originally created on Github. Cannot give you a PR as that would require me to violate my boycott of Github. I gave you a patch and the change is trivial. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [stash-pullrequest-builder-plugin] (JENKINS-29274) Comment log checker does not handle build names with regex special characters
Title: Message Title
Dale King created an issue
Jenkins / JENKINS-29274
Comment log checker does not handle build names with regex special characters
Issue Type:
Bug
Assignee:
nathan m
Components:
stash-pullrequest-builder-plugin
Created:
07/Jul/15 3:46 PM
Priority:
Major
Reporter:
Dale King
The regular expressions created for looking for build started and build finished message in the comments is inserting the build job name directly as part of the regular _expression_. That works if the build job name is a simple name, but in our case we had some text in parentheses in the name of the build job. The regex parser took that as a capture group so the match failed because it would not match the parentheses in the name.
You should use a capture group for the job name and then compare the captured text to the build job name or else use java.util.regex.Pattern.quote to add any necessary escape characters. Here is a patch that fixes it:
diff --git a/src/main/java/stashpullrequestbuilder/stashpullrequestbuilder/StashRepository.java b/src/main/java/stashpullrequestbuilder/stashpullrequestbuilder/StashRepository.java
index 2d9bf76..efca26d 100644
--- a/src/main/java/stashpullrequestbuilder/stashpullrequestbuilder/StashRepository.java
+++ b/src/main/java/stashpullrequestbuilder/stashpullrequestbuilder/StashRepository.java
@@ -157,8 +157,9 @@ public class StashRepository {
}
//These will match any start or finish message -- need to check commits
-String
[JIRA] [core] (JENKINS-19899) Add Build Now and Configure Project links to all pages within a job
Dale King commented on JENKINS-19899 Add Build Now and Configure Project links to all pages within a job Yes, Daniel I am aware of the faulty logic underlying the decision to not put these links on sub pages of the job, but restating that faulty logic does not make it valid. They are not completely different objects, they are sub objects of each other. Sure there should be some differentiation in the links between the actions to take at the job level and the sub page level but that does not justify removing the job level links. And no having to do target practice to hit that tiny little triangle to open up a submenu to then see the actions and click yet again is not good enough. Any level of usability testing would show that Build Now and Configure are the most often used actions taken on any job, followed by see the console of the latest build. Luckily we have plugins like extra columns which lets up put those actions directly on the dashboard but navigating within a job to these actions is still a pain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-19899) Add Build Now and Configure Project links to all pages within a job
Dale King edited a comment on JENKINS-19899 Add Build Now and Configure Project links to all pages within a job Yes, Daniel I am aware of the faulty logic underlying the decision to not put these links on sub pages of the job, but restating that faulty logic does not make it valid. They are not completely different objects, they are sub objects of each other. Sure there should be some differentiation in the links between the actions to take at the job level and the sub page level but that does not justify removing the job level links. And no, having to do target practice to hit that tiny little triangle to open up a submenu to then see the actions and click yet again is not good enough. Any level of usability testing would show that Build Now and Configure are the most often used actions taken on any job, followed by see the console of the latest build. Luckily we have plugins like extra columns which lets up put those actions directly on the dashboard but navigating within a job to these actions is still a pain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [testflight] (JENKINS-20503) Appending changlog says no changes if a build failed
Dale King
commented on JENKINS-20503
Appending changlog says no changes if a build failed
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file to build up to inject as environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:" TestFlightChanges
echo "" TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$i+1;
git log 1 "-format=format:$i. %s - %an\n" $hash TestFlightChanges
fi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build" TestFlightChanges
fi
echo "" TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" TestFlightChanges
echo "TestFlightChangeCount=$i" TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits.
I use the TestFlightChangeCount as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [testflight] (JENKINS-20503) Appending changlog says no changes if a build failed
Dale King
edited a comment on JENKINS-20503
Appending changlog says no changes if a build failed
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file to build up to inject as environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:\\" TestFlightChanges
echo "\\" TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$[i+1];
git log -1 "--format=format:$i. %s - %an\n" $hash TestFlightChanges
fi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build\\" TestFlightChanges
fi
echo "\\" TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" TestFlightChanges
echo "TestFlightChangeCount=$i" TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits.
I use the TestFlightChangeCount as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [testflight] (JENKINS-20503) Appending changlog says no changes if a build failed
Dale King
edited a comment on JENKINS-20503
Appending changlog says no changes if a build failed
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file to build up to inject as environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:\\" TestFlightChanges
echo "\\" TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$[i+1];
git log -1 "--format=format:$i. %s - %an\n" $hash TestFlightChanges
fi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build\\" TestFlightChanges
fi
echo "\\" TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" TestFlightChanges
echo "TestFlightChangeCount=$i" TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits.
Note that this relies on the existence of the tag, so you will need to add the initial tag yourself.
I use the TestFlightChangeCount as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [testflight] (JENKINS-20503) Appending changlog says no changes if a build failed
Dale King
edited a comment on JENKINS-20503
Appending changlog says no changes if a build failed
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" in the log (using Flexible Publish plugin) that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file containing environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:\\" TestFlightChanges
echo "\\" TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$[i+1];
git log -1 "--format=format:$i. %s - %an\n" $hash TestFlightChanges
fi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build\\" TestFlightChanges
fi
echo "\\" TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" TestFlightChanges
echo "TestFlightChangeCount=$i" TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits, which are not important for testers.
Note that this relies on the existence of the Jenkins-LastTestFlight tag, so you will need to add the initial tag yourself.
I use the TestFlightChangeCount variable as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.
Then just put ${TestFlightChangeLog} in your build notes box for TestFlight and turn off the standar broken change log.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Dale King
commented on JENKINS-17526
Broken CSS when reloading Jenkins after a time of inactivity
The answer is moving the temp dir for Jetty outside of the normal temp directory which gets periodically cleaned. If you examine Greg's pull request you can see which files to change to move the temp dir for jetty and I can confirm this fixes the problem.
To implement that solution is to edit /Library/Application Support/Jenkins/jenkins-runner.sh (you'll need su priveleges to do so) and add this line to the middle of the file near the lines that are similar:
tmpdir=`$defaults tmpdir` javaArgs="$javaArgs -Djava.io.tmpdir=${tmpdir}"
You'll need to create a temp directory for Jenkins (/Users/Shared/Jenkins/temp in my example) and give ownership to Jenkins:
sudo mkdir -p /Users/Shared/Jenkins/temp
sudo chown jenkins:jenkins /Users/Shared/Jenkins/temp
Then you need to set that directory as default:
defaults write /Library/Preferences/org.jenkins-ci tmpdir /Users/Shared/Jenkins/temp
Restart Jenkins and the problem will be gone for good.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [git] (JENKINS-20736) Git plugin does not update origin if URL changes
Dale King created JENKINS-20736 Git plugin does not update origin if URL changes Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 22/Nov/13 10:58 PM Description: I ran into a slight issue. Within my job I had a post build step that conditionally adds a tag and pushes it to origin. That was working until we renamed our git repo and thus changing the URL. I changed the URL in the job config, but the pushing of the tag was failing. The reason was that origin was never updated to the new URL because the builds did not do a new clone and the git plugin does not rely on the origin remote. Might be a good idea if the origin remote is updated to reflect the current URL. The workaround is that I need to not rely on origin in my job. Environment: Any Project: Jenkins Priority: Minor Reporter: Dale King This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [testflight] (JENKINS-20504) Add ability to specify a file as build notes
Dale King created JENKINS-20504 Add ability to specify a file as build notes Issue Type: Improvement Assignee: Unassigned Components: testflight Created: 10/Nov/13 3:16 AM Description: Partially as a workaround of JENKINS-20503 bug and because I would also like to filter the change log I would like to build up the build notes myself to send to Testflight using a script. The Testflight plugin does support expanding environment variables in the build notes, but going from a script that generates arbitrary multi-line text to an environment variable usable in other build steps in Jenkins is non-trivial. It would be nice to just bypass the environment variable and just use a file to generate the build notes for TestFlight. Environment: Any Project: Jenkins Priority: Major Reporter: Dale King This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [gradle] (JENKINS-20505) gradle build failed due to multiline build parameter
Dale King created JENKINS-20505 gradle build failed due to multiline build parameter Issue Type: Bug Assignee: Gregory Boissinot Components: gradle Created: 10/Nov/13 3:33 AM Description: I added a Build parameter of type text which contains multiline text for use by another plugin. For some reason, gradle plugindecided it needed to pass it gradle using -D options, but because the value was multiline the command is not valid Environment: Any Project: Jenkins Priority: Major Reporter: Dale King This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Dale King commented on JENKINS-13995 Would like the ability to disable hover-over context menus. In my opinion the pop-up menus that popped up with mouse hover were the PRIMARY ADVANTAGE that Jenkins had over Hudson! Bring them back! I can understand the need to allow it to be disabled, but not for getting rid of it entirely. The hover menus allowed me to get to almost anywhere in Jenkins with a single click. The new version is back to the multiple clicks and page loads to get anywhere that drove me crazy in Hudson. Note I will be upgrading to an older version until this is fixed. I wonder if it would be possible to restore old functionality with a grease monkey script This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [gradle] (JENKINS-18034) Gradle plugin does not handle spaces in Jenkins install location
Dale King created JENKINS-18034 Gradle plugin does not handle spaces in Jenkins install location Issue Type: Bug Assignee: Gregory Boissinot Components: gradle Created: 21/May/13 9:25 PM Description: I have Jenkins installed in Tomcat which is installed in C:\Program Files (x86). Gradle execution fails due to space in the path for temp directory: Gradle - Launching build. My Project $ cmd.exe /C '"C:\.jenkins\tools\hudson.plugins.gradle.GradleInstallation\Gradle-1.6\bin\gradle.bat --init-script C:/Program Files (x86)/Apache Software Foundation/Tomcat 7.0/temp/init-artifactory6084622070616493781gradle assemble artifactoryPublish exit %%ERRORLEVEL%%"' FAILURE: Build failed with an exception. What went wrong: Could not read initialization script 'C:\Program' as it does not exist. Environment: Windows 7 Project: Jenkins Priority: Major Reporter: Dale King This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [gradle] (JENKINS-18034) Gradle plugin does not handle spaces in Jenkins install location
Dale King commented on JENKINS-18034 Gradle plugin does not handle spaces in Jenkins install location Actually, now that I look at it is probably the artifactory plugin at fault. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
