Hi Mikael, what is the process if we want additional plug-ins for Jenkins?
For example, the Warnings-Plugin looks useful to me to validate via Gerrit verification builds, that the number of compiler warnings do not increase. References: https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin https://stackoverflow.com/questions/38308496/how-do-i-fail-a-build-in-jenkins-if-the-number-of-compiler-warnings-increases Best regards, Lars On Wed, Mar 14, 2018 at 9:43 AM, Mikaël Barbero < mikael.barb...@eclipse-foundation.org> wrote: > > 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. > > Thanks. > > -- > *Mikaël Barbero - *Eclipse Foundation > IT Services - Release Engineering > 📱 (+33) 642 028 039 > 📧 mikael.barb...@eclipse-foundation.org > 🐦 @mikbarbero > > > > > > On Mon, Mar 12, 2018 at 9:25 AM, Mikaël Barbero <mikael.barbero@eclipse- > foundation.org> wrote: > >> Hi, >> >> For those of you who use a JIPP to build Gerrit patch sets, you may have >> noticed that the user "Hudson CI" has been renamed to "CI Bot". This is >> purely cosmetic. >> >> Also, the documentation about how to setup the Gerrit trigger Jenkins >> plugin has been revamped and is now available here >> https://wiki.eclipse.org/Jenkins#Gerrit_Trigger_Plugin >> >> I would like to draw you attention to the possible triggers you can setup >> (https://wiki.eclipse.org/Jenkins#Configuration_of_Build_Triggers). Many >> of you want to re-trigger a build when it fails (e.g., because of flaky >> tests). It can be tedious to have to go to Jenkins just to do that. The >> Gerrit trigger Jenkins plugin is not only able to trigger a build on a new >> patch set. It lets you define triggers on comment values (e.g., if a >> comment contains "run CI"). Have a look at the previous link for an example. >> >> Cheers, >> >> >> -- >> *Mikaël Barbero - *Eclipse Foundation >> IT Services - Release Engineering >> 📱 (+33) 642 028 039 >> 📧 mikael.barb...@eclipse-foundation.org >> 🐦 @mikbarbero >> >> >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> > > > > -- > Nick Boldt > Senior Software Engineer, RHCSA > Productization Lead :: JBoss Tools & Dev Studio > > IM: @nickboldt / @nboldt / http://nick.divbyzero.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > @ @redhatnews <https://twitter.com/redhatnews> Red Hat > <https://www.facebook.com/RedHatInc> > <https://www.facebook.com/RedHatInc> > > > “The Only Thing That Is Constant Is Change” - Heraclitus > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > -- Eclipse Platform project co-lead CEO vogella GmbH Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
