That seems like the kind of decision any committer is empowered to make. Thus far, as a committer I have elected to leave all of the old jobs in place until the new ones are live because I'd personally consider having no nightly job with visibility to contributors as a blocker.
If you are unsure of your own stance for whatever reason, I'd recommend following the established community norm of starting a DISCUSS thread. On Fri, Oct 13, 2017 at 12:46 PM, Ted Yu <yuzhih...@gmail.com> wrote: > Does that mean https://builds.apache.org/job/HBase-1.3-JDK7 > <https://builds.apache.org/job/HBase-1.3-JDK7/307/console> should be > disabled ? > > On Fri, Oct 13, 2017 at 10:33 AM, Sean Busbey <bus...@apache.org> wrote: > >> Ted, if the problem isn't also happening on the new nightly builds[1] >> please just ignore it. >> >> The sooner we can get the new nightly jobs stable and turn off the old >> jobs the better for all of us. >> >> The problems that we already have tracked for the new nightly builds >> all show up as blockers of HBASE-18467. >> >> [1]: https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/ >> >> On Fri, Oct 13, 2017 at 12:12 PM, Ted Yu <yuzhih...@gmail.com> wrote: >> > Thanks for taking a look. >> > >> > Logged INFRA-15275 >> > >> > On Fri, Oct 13, 2017 at 10:09 AM, Mike Drob <md...@apache.org> wrote: >> > >> >> I am not able to reproduce that locally with JDK7, but maybe it has >> >> something to do with docker or the jenkins build environment not having >> the >> >> right things set up >> >> >> >> On Fri, Oct 13, 2017 at 10:52 AM, Ted Yu <yuzhih...@gmail.com> wrote: >> >> >> >> > Hi, >> >> > From https://builds.apache.org/job/HBase-1.3-JDK7/307/console : >> >> > >> >> > [ERROR] Failed to execute goal >> >> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce >> >> > (min-maven-min-java-banned-xerces) on project hbase: Execution >> >> > min-maven-min-java-banned-xerces of goal >> >> > org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce >> failed. >> >> > NullPointerException -> [Help 1] >> >> > >> >> > Does someone know what could have caused the above error ? >> >> > >> >> > Thanks >> >> > >> >> >>
