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
On Mon, Apr 30, 2018 at 8:34 PM, Sanne Grinovero
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 discu
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.
Alternatively:
- we could look at pipelines
- run all jobs within Docker -> improved isolat
Then we should move to a CI server that is not erroneously triggering jobs
it should not.
On Mon, Apr 30, 2018 at 11:30 AM Guillaume Smet
wrote:
> Hi,
>
> So, as expected, I'm not very happy with the new CI setup when doing
> releases.
>
> The issue is that each commit to ORM triggers at least 5
Hi,
So, as expected, I'm not very happy with the new CI setup when doing
releases.
The issue is that each commit to ORM triggers at least 5 jobs (5.0, 5.1,
5,2, master-h2, master-check) which takes all the slave bandwidth we have.
Note that I'm talking of ORM because it's where the issue is the
