Who can rework the Jenkins plugin we use, so that the build won't be triggered after Groovy libs have changed? Somebody changes [1] and [2] and then all 100 Maven projects run all bunch of branches. The queue is huge in Jenkins, and this is the blocker for the entire organization and not only for us Maven!
[1]: https://gitbox.apache.org/repos/asf?p=maven-jenkins-env.git [2]: https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git On Mon, Jun 17, 2019 at 7:16 PM Robert Scholte <rfscho...@apache.org> wrote: > Sure, will investigate. > > thanks, > Robert > > On Mon, 17 Jun 2019 15:21:30 +0200, Robert Munteanu <romb...@apache.org> > wrote: > > > Hi, > > > > I noticed today that Jenkins is taking more time to start building > > various jobs. Looking at the executors, I think there is a > > misconfiguration/problem with some Maven-related jobs > > > > - > > https://builds.apache.org/job/maven-box/job/maven/job/MNG-6672/6/console > > > > This was started 3d17h ago. > > > > - > > > https://builds.apache.org/job/maven-box/job/maven-resolver/job/MRESOLVER-12/6/console > > > > This was started 4d4h ago > > > > - > > https://builds.apache.org/job/maven-box/job/maven/job/master/226/console > > > > This was started 1d16h ago. > > > > And quite some more, but I guess you get the point :-) It would be > > great if someon from the Maven project could look into this. > > > > Thanks! > > > > Robert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
