Using docker might be a nice idea if the machines are powerful enough. I will just mention it here but for the release only we can also not use Jenkins and run the command we need from the terminal of ci.hibernate.org. We already have the scripts ready so it shouldn't be too hard.
If the Jenkins plugin doesn't work the way we need I don't feel like creating our own branch and I will consider it only if it's about sending a PR somewhere. But all this won't solve the problem with SourceForge that seems to be the main reason we see failures lately. On Mon, Apr 30, 2018 at 7:42 PM, Guillaume Smet <guillaume.s...@gmail.com> wrote: > On Mon, Apr 30, 2018 at 8:34 PM, Sanne Grinovero <sa...@hibernate.org> > wrote: > >> Starting a new slave only takes 3 minutes, but I believe it has to be >> a "manual start" from its admin dashboard as Jenkins's scaling plugin >> is limited. >> >> Fixing the Jenkins triggers would be my preference. >> > > Yeah, last time we discussed this on HipChat, I have all the useful > pointers. The code changes to the official plugin would be minimal. The > only thing I'm worried about is how we would maintain this plugin. > > Alternatively: >> - we could look at pipelines >> > > How would they solve the issue? > > >> - run all jobs within Docker -> improved isolation would allow us to >> run N builds per machine >> > > Would that help? I.e. are the machines we start powerful enough to run > several jobs in parallel? > > I suspect, it wouldn't change the issue, just change the numbers of servers > we would need (which might be good anyway but is not related to the issue > at hand). > > -- > Guillaume > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
