Il giorno sab 12 gen 2019 alle ore 11:45 Enrico Olivelli <[email protected]> ha scritto: > > > > Il sab 12 gen 2019, 11:39 Tibor Digana <[email protected]> ha scritto: >> >> Such a drastic change? > > > If that version is buggy we should fix it or drop it. > > Do we have already released that buggy version to users? > > > How did you see our processes on Jenkins slave? Do you have access to slaves > console? >
b.q. which commit could have broken shared utils ? https://github.com/apache/maven-shared-utils/commits/master Enrico > Enrico > > >> First we should get the confidence using Jenkins CI for a long time run. >> >> On Sat, Jan 12, 2019 at 11:20 AM Enrico Olivelli <[email protected]> >> wrote: >> >> > Can't we rollback to the previous version instead of a snapshot? >> > >> > Enrico >> > >> > Il sab 12 gen 2019, 09:23 Tibor Digana <[email protected]> ha >> > scritto: >> > >> > > 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 >> > > >> > -- >> > >> > >> > -- Enrico Olivelli >> > > > -- > > > -- Enrico Olivelli --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
