Jenkins going haywire ?

2020-08-27 Thread Gilles Sadowski
Hi. Something happening recently (apparently unrelated to changes in the repository): https://ci-builds.apache.org/job/Commons/job/commons-statistics/3/console https://ci-builds.apache.org/job/Commons/job/commons-numbers/2/console https://ci-builds.apache.org/job/Commons/job/commons-rng/3/co

RE: Jenkins going haywire ?

2020-08-27 Thread Uwe Schindler
We have seen the same for Lucene. The very useful and very important "Tools Environment" plugin is going crazy. This looks like a bug in this useful plugin. In most cases requires a Jenkins restart to recover. In most cases those messages repeat up to 10 times, but this looks like it’s a loop.

Re: Process Jenkins DSL action

2020-08-27 Thread Enrico Olivelli
Gavin, I am still blocked here: "Warning: Plugins have been installed without restarting Jenkins. A restart is required to run Job DSL without any problems. ERROR: You must configure the DSL job to run as a specific user in order to use the Groovy sandbox." Do you have any suggestions ? Thanks Enr

Re: Jenkins going haywire ?

2020-08-27 Thread Matt Sicker
This is what I'm doing as a workaround for the tool DSL as it wasn't working as expected in a complex pipeline I had: https://github.com/apache/logging-pipelines/blob/master/vars/mvn.groovy On Thu, 27 Aug 2020 at 06:36, Uwe Schindler wrote: > > We have seen the same for Lucene. The very useful a