Yup I updated https://issues.apache.org/jira/browse/INFRA-17514 with some
details.
so we have to wait next Jenkins plugins upgrade before reactivate it.
Note there is always a bloody committer who do not use bloody windauze to
develop... :)

On Tue, 15 Jan 2019 at 06:54, Robert Scholte <rfscho...@apache.org> wrote:

> I've removed the invokerPublisher() calls in our Jenkins scripts, this
> seems to be the cause of the hanging Java processes.
> Within a couple of hours I expect all Windows nodes to be restarted by
> INFRA and then we should be good again.
>
> thanks,
> Robert
>
> On Sat, 12 Jan 2019 09:23:20 +0100, Tibor Digana <tibordig...@apache.org>
>
> wrote:
>
> > I think we should downgrade maven-shared-utils to 3.1.0 in the
> > m-invoker-p
> > because we found the same problem in surefire:3.0.0-M1.
> > We did not have time to fix it and I have realized the connection to the
> > Invoker just now.
> > Faster than a release is to deploy SNAPSHOT version of the Invoker and
> > use
> > it in JAR plugin and we will see again fully working Jenkins build
> >
> https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/
> > The precondition is to ask the INFRA to restart all Windows or kill all
> > Java processes.
> > T
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Reply via email to