Re: [cross-project-issues-dev] Gerrit and Jenkins, tips and news
I would argue that the more tedious problem is having tests that sometimes fail. I've been waging a war against intermittent test failures in JBoss Tools for years. Some have been fixed by rewriting, some removed, and some fixed by upgrading the infrastructure (eg., giving slave nodes more RAM or more disk).
I can't agree more that flaky tests should be addressed at all costs. But it's a reality today, and having to re-trigger build of gerrit patchsets from Jenkins can be tedious. This is just a little help (that shall not hinder the effort to eradicate flaky tests)
Another way to manage this problem is to install the Naginator plugin to your JIPP: "Naginator is a plugin that schedules a new build immediately following a build failure, thereby nagging the project members that the build is failing." Can be configured to define number of rebuilds, frequency of rebuilds, etc.
It is probably perfectly reasonable to run this plugin on the RedHat build infra, but I must forbid this plugin on the Eclipse infra for the foreseeable future. Some projects are already experiencing huge variation on their build time during peak hours, such a plugin would just make it worse for everybody.
We are working on isolating projects one from each other. Until then, thank you for not using Naginator or similar plugin.
Mikaël Barbero - Eclipse Foundation
IT Services - Release Engineering
📱 (+33) 642 028 039
cross-project-issues-dev mailing listcross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Description: Message signed with OpenPGP