[JIRA] (JENKINS-50740) gitlabCommitStatus clobbers Groovy compilation exceptions
Title: Message Title Andrew Bayer commented on JENKINS-50740 Re: gitlabCommitStatus clobbers Groovy compilation exceptions So I think the problem is in here. Though I may not be quite right. What's happening is that the compilation exception from load is getting serialized as part of the program state, but I'm not entirely sure how/why. 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 Owen Mehegan commented on JENKINS-50740 Re: gitlabCommitStatus clobbers Groovy compilation exceptions Andrew Bayer any chance you could give me a pointer about how gitlab-plugin might handle this scenario more gracefully? I'm surprised that something we do causes the more useful exception to be swallowed. 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 Andrew Bayer updated an issue Jenkins / JENKINS-50740 gitlabCommitStatus clobbers Groovy compilation exceptions Change By: Andrew Bayer Component/s: pipeline 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
