[JIRA] (JENKINS-49776) Multiple duplicate "Label This Build" links in workflow sidebar for Pipeline project with P4
Title: Message Title Max M commented on JENKINS-49776 Re: Multiple duplicate "Label This Build" links in workflow sidebar for Pipeline project with P4 The same story, but with Git: JENKINS-29326 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29326) Workflow sidebar has duplicated Git Build Data links
Title: Message Title Max M edited a comment on JENKINS-29326 Re: Workflow sidebar has duplicated Git Build Data links May I ask why is this *Priority: Minor*?Can this be escalated?There are like +dozens+ of duplicates of this issue (see e.g. JENKINS-38204 -- – the SVN lineage of dupes), and it looks like it's getting "fixed", then broken, then fixed again, then broken again... Is this an architectural problem in Jenkins?Can anybody fix this one once -and-for-all? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38204) SVN plugin show all checkouts twice in pipeline project
Title: Message Title Max M commented on JENKINS-38204 Re: SVN plugin show all checkouts twice in pipeline project Looks like this is not specific to SVN. JENKINS-29326, by the looks of it, is the very same [bunch of duplicate] issue(s), but reported with Git. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29326) Workflow sidebar has duplicated Git Build Data links
Title: Message Title Max M commented on JENKINS-29326 Re: Workflow sidebar has duplicated Git Build Data links May I ask why is this Priority: Minor? Can this be escalated? There are like dozens of duplicates of this issue (see e.g. JENKINS-38204 – the SVN lineage of dupes), and it looks like it's getting "fixed", then broken, then fixed again, then broken again... Is this an architectural problem in Jenkins? Can anybody fix this one-and-for-all? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Title: Message Title Max M commented on JENKINS-40109 Re: Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector Reported as JENKINS-50740. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50740) gitlabCommitStatus clobbers Groovy compilation exceptions
Title: Message Title
Max M updated an issue
Jenkins / JENKINS-50740
gitlabCommitStatus clobbers Groovy compilation exceptions
Change By:
Max M
With Declarative Pipelines, one can use {{gitlabCommitStatus}} action in Groovy scripts.An issue has been found (see comments in JENKINS-40109), that whenever the nested script aborts with a runtime Groovy compilation error, {{gitlabCommitStatus}} obscures the real exception information, complicating diagnosis significantly.A minimal example Pipeline script displaying the problem:{code}node('build-server') { gitlabCommitStatus { stage('CI fail test') {sh('echo IP=10.0.0.1 > test_env')load('test_env') } }}{code}With {{gitlabCommitStatus}} wrapper present, the build log is:{code}[Pipeline] nodeRunning on build- server3 server in /home/jenkins/workspace/test[Pipeline] {[Pipeline] gitlabCommitStatus[Pipeline] {[Pipeline] stage[Pipeline] { (CI fail test)[Pipeline] sh[test] Running shell script+ echo IP=10.0.0.1[Pipeline] load[Pipeline] // load[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // gitlabCommitStatus[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinean exception which occurred: in field org.codehaus.groovy.control.MultipleCompilationErrorsException.collector in object org.codehaus.groovy.control.MultipleCompilationErrorsException@46bfd811 in field com.cloudbees.groovy.cps.Outcome.abnormal in object com.cloudbees.groovy.cps.Outcome@5f72c919 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.outcome in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@6acbb027 in field com.dabsquared.gitlabjenkins.workflow.GitLabCommitStatusStep$GitLabCommitStatusStepExecution.body in object com.dabsquared.gitlabjenkins.workflow.GitLabCommitStatusStep$GitLabCommitStatusStepExecution@4a45f799 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@39b722f2 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.thread in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@7acf4f5a in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.this$0 in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter@728f1fb3 in field com.cloudbees.groovy.cps.impl.CallEnv.returnAddress in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@443e9627 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.TryBlockEnv@67fdf6be in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@666d0269 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@29e2337c in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@3d03cc7a in field com.cloudbees.groovy.cps.impl.CpsClosureDef.capture in object com.cloudbees.groovy.cps.impl.CpsClosureDef@169b393b in field com.cloudbees.groovy.cps.impl.CpsClosure.def in object
[JIRA] (JENKINS-50740) gitlabCommitStatus clobbers Groovy compilation exceptions
Title: Message Title
Max M created an issue
Jenkins / JENKINS-50740
gitlabCommitStatus clobbers Groovy compilation exceptions
Issue Type:
Bug
Assignee:
Owen Mehegan
Components:
gitlab-plugin, pipeline
Created:
2018-04-11 14:20
Environment:
gitlab plugin & declarative pipelines
Priority:
Major
Reporter:
Max M
With Declarative Pipelines, one can use gitlabCommitStatus action in Groovy scripts. An issue has been found (see comments in JENKINS-40109), that whenever the nested script aborts with a runtime Groovy compilation error, gitlabCommitStatus obscures the real exception information, complicating diagnosis significantly. A minimal example Pipeline script displaying the problem:
node('build-server') {
gitlabCommitStatus {
stage('CI fail test') {
sh('echo IP=10.0.0.1 > test_env')
load('test_env')
}
}
}
With gitlabCommitStatus wrapper present, the build log is:
[Pipeline] node
Running on build-server3 in /home/jenkins/workspace/test
[Pipeline] {
[Pipeline] gitlabCommitStatus
[Pipeline] {
[Pipeline] stage
[Pipeline] { (CI fail test)
[Pipeline] sh
[test] Running shell script
+ echo IP=10.0.0.1
[Pipeline] load
[Pipeline] // load
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // gitlabCommitStatus
[Pipeline] }
[Pipeline] // node
[Pipeline] End of
[JIRA] (JENKINS-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Title: Message Title
Max M commented on JENKINS-40109
Re: Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Hey Andrew Bayer! I've succeeded in minimizing the reproducing config for my case:
node('build-server') {
gitlabCommitStatus {
// try {
stage('CI fail test') {
sh('echo IP=10.0.0.1 > test_env')
load('test_env')
}
// }
// catch (java.lang.Throwable error) {
// println "exception caught"
// println error
// throw error
// }
}
}
It seems that gitlabCommitStatus wrap is essential here: without it, exception details are clear and informative in the log. With it, I get NotSerializableException as above. The exact compile error trigger is less important: here, it's that IP=10.0.0.1 isn't valid Groovy. Of course, this could've been a legitimate Groovy CI module load, perhaps with a syntax error as well. The commented try-catch is a workaround I found which helps to see the actual compile error. Might it be a gitlabCommitStatus bug?.. I don't even know which plugin is that from, sorry about that. Anyway, hope this helps!
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-40109) Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector
Title: Message Title Max M commented on JENKINS-40109 Re: Compilation error in shared library/global variable produces java.io.NotSerializableException org.codehaus.groovy.control.ErrorCollector I am as well getting the same ErrorCollector NotSerializable exception; however, a standalone call like this: $ groovy CI/erroring_script.groovy $ (outside of Jenkins) does not show any compilation errors! In Jenkins, OTOH, this same file causes stacktraces like this: an exception which occurred: in field org.codehaus.groovy.control.MultipleCompilationErrorsException.collector in object org.codehaus.groovy.control.MultipleCompilationErrorsException@5c35f1cb in field com.cloudbees.groovy.cps.Outcome.abnormal in object com.cloudbees.groovy.cps.Outcome@3bd3307c in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.outcome in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@5ea1a9f6 in field com.dabsquared.gitlabjenkins.workflow.GitLabCommitStatusStep$GitLabCommitStatusStepExecution.body in object com.dabsquared.gitlabjenkins.workflow.GitLabCommitStatusStep$GitLabCommitStatusStepExecution@1d84ca28 in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@57923e5c in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.thread in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@1509e249 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.this$0 in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter@66aabd0b in field com.cloudbees.groovy.cps.impl.CallEnv.returnAddress in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@4ece610f in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.TryBlockEnv@164ca394 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@5e76c9db in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@147a91d1 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@1e88ca58 in field com.cloudbees.groovy.cps.impl.CpsClosureDef.capture in object com.cloudbees.groovy.cps.impl.CpsClosureDef@34f25659 in field com.cloudbees.groovy.cps.impl.CpsClosure.def in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@15439a64 in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.closures in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@89104e8 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@89104e8 Caused: java.io.NotSerializableException: org.codehaus.groovy.control.ErrorCollector at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at
