On Fri, Oct 14, 2016 at 6:04 AM, Jonathan Hodgson wrote:
> 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
In general, do not go looking for fun and exciting Groovy language
features. Keep to the basics:
> 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.
>
>
>
> > 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
> 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 descr
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
Hi,
Groovy in Jenkins has some quirks and they're really driving me nuts.
Some of the very neat features of Groovy, such as closures and .each() and
.findAll() don't work as advertised. Which is a problem because it's these
neat ways of doing things that are always used when you google a proble
