technology.recommenders Plugin Hudson

Hudson Continuous Integration Engine

Hudson instance [NA] is located at

There are 10 jobs defined on this instance. 8 are green (stable), 0 are yellow (unstable), 2 are red (failing).


The following metrics are available:

  • Number of jobs defined on the host (CI_JOBS): 10.
  • Number of jobs in status failed for more than one week (CI_JOBS_FAILED_1W): 1.
  • Number of jobs in status green (CI_JOBS_GREEN): 8.
  • Number of jobs in status yellow (CI_JOBS_YELLOW): 0.
  • Number of jobs in status red (CI_JOBS_RED): 2.


Failing Jobs

There are 2 failing jobs on the instance.

These jobs have not been failing for a long time (less than a week). It should be quite easy to make them succeed again. Fix them as soon as possible.

  • org.eclipse.recommenders-sonar has been failing for 3 days.

These jobs have been failing for quite a long time (more than a month). Constantly failing builds are not good for build confidence. They should be disabled if they are not relevant anymore, or if you think they still have some value then fix them.

  • org.eclipse.recommenders.snipmatch-gerrit has been failing for 157 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
org.eclipse.recommenders-sonar 2017-04-22 00:00:45 935 sec. 50 %
org.eclipse.recommenders.snipmatch-gerrit 2016-12-02 04:55:07 320 sec. 20 %

Unstable Jobs

A build is considered unstable if it was built successfully and one or more publishers report it unstable. For example if the JUnit publisher is configured and a test fails then the build will be marked unstable.

One of the purpose of continuous integration is to provide confidence in builds and deliveries, so unstability is not an option. Fix them, or disable the failing publishers if they are not relevant anymore. This list should be generally empty, or at least a temporary, time-limited stage for builds.

Unstable jobs
Name Last Build Last Duration Stability

Successful Jobs

These jobs run well, congrats!

Maybe you could check from time to time if this criterion is still relevant: are the builds succeeding because they measure the wrong thing, because the build is outdated and doesn’t evolve anymore, or because things are plainly right?

OK jobs
Name Last Build Last Duration Stability
org.eclipse.recommenders-gerrit 2017-04-12 04:34:44 2292 sec. 40 %
org.eclipse.recommenders-maintenance 2017-04-22 00:00:46 3141 sec. 80 %
org.eclipse.recommenders-master 2017-04-22 00:00:46 5232 sec. 80 %
org.eclipse.recommenders.privacy 2017-04-22 00:00:45 220 sec. 100 %
org.eclipse.recommenders.privacy-gerrit 2016-11-20 13:15:07 166 sec. 100 %
org.eclipse.recommenders.snipmatch 2017-04-22 00:00:45 448 sec. 40 %
org.eclipse.recommenders.stats 2017-04-22 00:00:46 364 sec. 80 %
org.eclipse.recommenders.stats-gerrit 2016-11-16 04:38:47 2775 sec. 80 %

Page generated by Alambic 3.3 on Wed Aug 23 23:09:55 2017.