accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <ctubb...@apache.org>
Subject Re: Failing Jenkins?
Date Wed, 14 Jun 2017 17:52:02 GMT
Looks like an upgrade to Maven 3.5.0 broke the "Maven 3 (latest)" selection
in Jenkins and the "Maven (latest)" one. Switching to "Maven 3.3.9" seems
to do the trick.

On Tue, Jun 13, 2017 at 9:42 PM Christopher <ctubbsii@apache.org> wrote:

> Not sure which Java and label combination we're supposed to be using.
> Those settings worked before.
>
> On Tue, Jun 13, 2017, 20:34 Mike Drob <mdrob@apache.org> wrote:
>
>> java.io.IOException
>> <http://stacktrace.jenkins-ci.org/search?query=java.io.IOException>:
>> Cannot run program "/usr/lib/jvm/java-8-openjdk-amd64//bin/java" (in
>> directory "/home/jenkins/jenkins-slave/workspace/Accumulo-Master"):
>> error=2, No such file or directory
>>
>>
>>
>> On Tue, Jun 13, 2017 at 7:32 PM, Christopher <ctubbsii@apache.org> wrote:
>>
>> > Does anybody know what's wrong with Jenkins on builds.apache.org?
>> > Nearly all of our normal Maven jobs seem to fail, and have been failing
>> for
>> > nearly 2 weeks.
>> > It could be a misconfiguration, but it seems more likely it's Jenkins.
>> It's
>> > definitely not test failures. It's not even getting that far.
>> >
>> > I've already looked once. If somebody else could take a peek, I'd
>> > appreciate it, since I don't have time to look into it this week.
>> >
>> > https://builds.apache.org/view/A/view/Accumulo/
>> >
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message