Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
From: Christopher <ctubbsii@apache.org>
Date: Thu, 30 Nov 2017 23:42:21 +0000
Message-ID: <CAL5zq9abU7bn8zygppbzChiS6KvfWfDJJ=+vkS-JsJquw1J_vw@mail.gmail.com>
Subject: Jenkins failures with Maven 3.5.x
To: Users <users@infra.apache.org>, accumulo-dev <dev@accumulo.apache.org>
Content-Type: multipart/alternative; boundary="94eb2c0e9c7645ece1055f3bce6b"
archived-at: Thu, 30 Nov 2017 23:42:35 -0000

--94eb2c0e9c7645ece1055f3bce6b
Content-Type: text/plain; charset="UTF-8"

Accumulo Devs (and INFRA team),

Builds have been failing lately because of a recent Jenkins bug[1] with
Maven 3.5.x versions, even when Maven finished successfully. I moved our
jobs[2] back to build with Maven 3.3.9 as a workaround. Another workaround
would have been to disable the "Publish FindBugs analysis results"
checkbox, which seems to trigger the problem. This might make sense for us
anyway, since we already fail the build on new non-trivial findbugs issues.

Here's an example of a recent failure[3].

Including INFRA on this thread, in case it affects decisions to remove old
versions of Maven or otherwise affects Jenkins maintenance in any way.

[1]: https://issues.jenkins-ci.org/browse/JENKINS-44870
[2]: https://builds.apache.org/view/A/view/Accumulo/
[3]:
https://builds.apache.org/view/A/view/Accumulo/job/Accumulo-1.8/233/console

--94eb2c0e9c7645ece1055f3bce6b--