Thanks Mikael. Opened: https://bugs.eclipse.org/bugs/show_bug.cgi?id=532646
On Tue, Mar 20, 2018 at 11:05 AM, Mikaël Barbero <
mikael.barb...@eclipse-foundation.org> wrote:
> Simply open a bug against Community > CI Jenkins (
> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=
>
Simply open a bug against Community > CI Jenkins
(https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community=CI-Jenkins)
asking for specific plugin to be installed. You will have to configure your
jobs to use the plugin though.
Cheers,
--
Mikaël Barbero - Eclipse Foundation
IT Services -
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
> 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
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
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
