technology.ease Plugin Hudson



Hudson Continuous Integration Engine

Hudson instance [NA] is located at https://hudson.eclipse.org/ease.

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

Metrics

The following metrics are available:

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

History

Failing Jobs

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

  • No job failing for more than a week!

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability

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
ease-build-core 2017-04-21 23:13:43 304 sec. 100 %
ease-build-module-doclet 2017-04-19 22:49:43 18 sec. 100 %
ease-build-modules 2017-04-21 23:13:43 332 sec. 80 %
ease-core-sonar 2017-04-16 00:01:38 1011 sec. 66 %
ease-modules-sonar 2017-04-16 00:01:38 755 sec. 66 %
ease-nightly 2017-04-21 23:13:38 0 sec. 100 %
ease-release 2017-01-13 01:51:05 567 sec. 100 %
ease-verify-core 2017-04-19 08:11:09 165 sec. 100 %
ease-verify-modules 2017-04-10 05:13:03 90 sec. 60 %

Page generated by Alambic 3.3 on Fri Jun 23 11:33:44 2017.