Re: Re: Build failed in Jenkins: Commons-Codec #3

2016-06-07 Thread Dennis Kieselhorst
Am 07.06.2016 um 01:58 schrieb Gary Gregory: > On Mon, Jun 6, 2016 at 4:48 PM, Ralph Goers > wrote: > >> If that file is bad I would suspect every build running on that server >> would be failing. The server is jenkins-test-c83. As you know we were >> told not to use any of the jerkins-test serv

Re: Build failed in Jenkins: Commons-Codec #3

2016-06-06 Thread Matt Sicker
>From what I could tell about the jenkins test instances, they don't seem to be properly set up with repository.apache.org, so it's only the upload stage that fails on them. On 6 June 2016 at 18:58, Gary Gregory wrote: > On Mon, Jun 6, 2016 at 4:48 PM, Ralph Goers > wrote: > > > If that file is

Re: Build failed in Jenkins: Commons-Codec #3

2016-06-06 Thread Gary Gregory
On Mon, Jun 6, 2016 at 4:48 PM, Ralph Goers wrote: > If that file is bad I would suspect every build running on that server > would be failing. The server is jenkins-test-c83. As you know we were > told not to use any of the jerkins-test servers for our log4j builds. I > went ahead and changed

Re: Build failed in Jenkins: Commons-Codec #3

2016-06-06 Thread Ralph Goers
If that file is bad I would suspect every build running on that server would be failing. The server is jenkins-test-c83. As you know we were told not to use any of the jerkins-test servers for our log4j builds. I went ahead and changed to server restrictions to match what we use for log4j. R