Re: Build failed in Jenkins: Log4j 2.x #3005

2017-08-21 Thread Matt Sicker
Can we build inside Docker containers on Jenkins? This would make controlling specific compiler versions a lot easier (plus we can make an array of versions to automatically run tests on that way). On 21 August 2017 at 00:58, Apache wrote: > I guess it was changed

Re: Build failed in Jenkins: Log4j 2.x #3005

2017-08-20 Thread Apache
I guess it was changed from getPid() to pid() after 156. I will have to see if Jenkins has a newer release. Sent from my iPad > On Aug 20, 2017, at 7:51 PM, Apache Jenkins Server > wrote: > > See >

Re: Build failed in Jenkins: Log4j 2.x #3005

2017-08-20 Thread Remko Popma
Yes, renamed in build 166 apparently. https://bugs.openjdk.java.net/browse/JDK-8178347 On Mon, Aug 21, 2017 at 13:40 Remko Popma wrote: > Jenkins may be using an old Java 9: > > JDK[/home/jenkins/tools/java/jigsaw-jdk-9-ea-b156] > > Also, it seems this method was

Re: Build failed in Jenkins: Log4j 2.x #3005

2017-08-20 Thread Remko Popma
Jenkins may be using an old Java 9: JDK[/home/jenkins/tools/java/jigsaw-jdk-9-ea-b156] Also, it seems this method was previously called `getPid`. It must have been renamed recently. http://www.javaworld.com/article/3176874/java-language/java-9s-other-new-enhancements-part-3.html On Mon, Aug

Build failed in Jenkins: Log4j 2.x #3005

2017-08-20 Thread Apache Jenkins Server
See Changes: [rgoers] Add missing license header. Message should implement -- Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment