Andriy, You now have access to configure the jobs.
I've reconfigured the JDK18 job to show timestamps. I also changed the time out strategy from absolute to no activity. Still needs tweaking. Though I agree a 3 hour build is not good. John On Sat, May 5, 2018 at 9:48 AM Andriy Redko <drr...@gmail.com> wrote: > Hey guys, > > I think many of you noticed that builds on Jenkins ( > https://builds.apache.org/job/CXF-Trunk-JDK18/, > https://builds.apache.org/job/CXF-Trunk-PR/) > started to take much longer (more than 3 hours) and eventually are aborted > due to timeout (the last one we have is dated April 24th). Anyone has > looked at it or has an idea why it started to happen? I don't have access > to Jenkins configuration, but if someone could assist with adding the > Timestamper (https://plugins.jenkins.io/timestamper), it would help to > capture the timeline. The agents builds are run on seem to be the same. > > On another topic, since JDK9 is end of life, do we need to keep > https://builds.apache.org/job/CXF-Master-JDK9/ active? > Thanks! > > Best Regards, > Andriy Redko > > > > > > >
