modeling.sirius Plugin Hudson

Hudson Continuous Integration Engine

Hudson instance [NA] is located at

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


The following metrics are available:

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


Failing Jobs

There are 8 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.

  • No job failing for less than a week!

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.

  • ecoretools-2.0 has been failing for 26856 hours.
  • ecoretools-3.1 has been failing for 13291 hours.
  • sirius-website-check has been failing for 23968 hours.
  • sirius.rcptt-master has been failing for 422311 hours.
  • sirius.sonar-master has been failing for 38 hours.
  • sirius.tests-master has been failing for 32 hours.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
ecoretools-2.0 2018-01-16 02:18:05 18 sec. 50 %
ecoretools-3.1 2018-01-16 02:12:09 168 sec. 33 %
sirius-website-check 2018-02-02 21:20:09 8 sec. 0 % 2018-03-05 15:30:37 183 sec. 80 %
sirius.gerrit.tests-oxygen 2018-03-05 15:49:23 1805 sec. 0 %
sirius.rcptt-master 2017-10-23 09:09:06 3087 sec. 0 %
sirius.sonar-master 2018-03-05 12:15:55 1204 sec. 80 %
sirius.tests-master 2018-03-05 18:00:00 3606 sec. 60 %

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
ecoretools-3.2 2018-01-16 02:12:09 267 sec. 99 %
ecoretools-master 2018-02-28 02:12:06 107 sec. 99 %
ecoretools.gerrit 2018-02-27 03:41:47 162 sec. 99 %
sirius.gerrit.tests-luna 2017-01-23 11:22:27 1418 sec. 80 %
sirius.tests2-master 2018-02-26 08:07:53 6771 sec. 80 %

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

Page generated by Alambic 3.3.3-dev on Fri Mar 23 05:22:16 2018.