Re: Why does Groovy seem to be so broken in jenkins?

[Daniel Beck]

> On 14.10.2016, at 12:04, Jonathan Hodgson  wrote:
> 
> at some point in the various updates of jenkins and the pipeline plugins it 
> appears to have broken stuff that was previously working. Things actually 
> seem to be getting worse!

Hopefully it's a one-time thing:

https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Groovy+Plugin#PipelineGroovyPlugin-2.14%28Sep07,2016%29

Although that changelog admittedly does look scary…

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/798F1DC5-D876-490A-B913-A92B8C142A17%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Why does Groovy seem to be so broken in jenkins?

[Jonathan Hodgson]

>
>
>
> > But the problem I described as a case in point doesn't seem to fall 
> under that umbrella. 
>
> Explanation here: 
> https://github.com/jenkinsci/workflow-cps-plugin/#technical-design 
>
>
>
Thanks. that helps explain things.

Though my confusion is increased by the fact that right now I'm having to 
go through previously tested and working code and move stuff to @NonCPS 
functions, because at some point in the various updates of jenkins and the 
pipeline plugins it appears to have broken stuff that was previously 
working. Things actually seem to be getting worse!

It's a shame that pipeline plugin doesn't at least recognize errors that 
might be related to this issute and add some useful information to the 
error message, such as a suggestion to look at that explanation you linked 
to. As a newbie to Groovy I have wasted so much time looking for errors in 
my groovy code, when in fact I had written perfectly valid groovy, just the 
pipeline implementation couldn't handle it.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/951bfad4-6ea0-4061-bfc3-f43d121f80ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why does Groovy seem to be so broken in jenkins?

[Daniel Beck]

> On 13.10.2016, at 20:28, Jonathan Hodgson  wrote:
> 
> since this is not user error I'm talking about, but bugs in the 
> implementation, I thought that the development forum was the correct one.

This topic is about using Jenkins, therefore a topic for the users list.

> But the problem I described as a case in point doesn't seem to fall under 
> that umbrella. 

Explanation here: 
https://github.com/jenkinsci/workflow-cps-plugin/#technical-design


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/469E284A-80C2-4697-A12A-E9ACB28E7F3D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Why does Groovy seem to be so broken in jenkins?

[Jonathan Hodgson]

On Thursday, October 13, 2016 at 6:59:16 PM UTC+1, Baptiste Mathus wrote:
>
> Hi, please use the users list if this is to discuss Pipeline usage.
>

I'm sorry, since the big selling point of Jenkins 2 was that pipelines are 
now integral to the Jenkins plan, and since this is not user error I'm 
talking about, but bugs in the implementation, I thought that the 
development forum was the correct one.
 

> Also, don't mix up the Groovy flavour in use with Pipeline, and the one 
> (standard) you can use in the script console, as job steps, and so on.
>

I didn't actually realize there were two, thanks for informing me, but 
since the pipeline is where I actually have to do my work, that doesn't 
help me much.
 

>
> What you seem to describe is "just" a known issue: 
> https://issues.jenkins-ci.org/browse/JENKINS-26481 
> 
>  
> (though, granted, an important when you don't know about it).
>
>
It doesn't seem so to me, some of what I talked about is that known issue, 
the problem with closures. But the problem I described as a case in point 
doesn't seem to fall under that umbrella. 

I've managed to work around the known issue, but this new problem, I don't 
even have a clue. When adding a couple of lines of simple and unrelated 
code cause a regex matcher to suddenly break, I don't even know where to 
start working out what's going on.

regards

Jon

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/955a5cc4-d638-4899-85f8-a64c0e83bfbd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.