technology.hudson Plugin Hudson



Hudson Continuous Integration Engine

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

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

Metrics

The following metrics are available:

  • Number of jobs defined on the host (JOBS): 14.
  • Number of jobs in status failed for more than one week (JOBS_FAILED_1W): 11.
  • Number of jobs in status green (JOBS_GREEN): 0.
  • Number of jobs in status yellow (JOBS_YELLOW): 0.
  • Number of jobs in status red (JOBS_RED): 11.

History

Failing Jobs

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

  • hudson-core has been failing for 314 days.
  • hudson-core-ee7-support has been failing for 201 days.
  • hudson-maven-hpi-plugin has been failing for 201 days.
  • hudson-remoting has been failing for 201 days.
  • hudson-stapler has been failing for 201 days.
  • hudson-test-harness has been failing for 17241 days.
  • maven3-support has been failing for 201 days.
  • plugin_git has been failing for 17241 days.
  • plugin_subversion has been failing for 17241 days.
  • rest-support has been failing for 201 days.
  • webmaster-test-osee-dev has been failing for 17241 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
hudson-core 2016-11-23 07:14:57 33 sec. 80 %
hudson-core-ee7-support 2016-11-23 07:15:32 31 sec. 80 %
hudson-maven-hpi-plugin 2016-11-23 07:15:30 0 sec. 60 %
hudson-remoting 2016-11-23 07:15:30 1 sec. 60 %
hudson-stapler 2016-11-23 07:15:31 2 sec. 60 %
hudson-test-harness 2017-03-15 00:01:18 4238 sec. 0 %
maven3-support 2016-11-23 07:15:31 5 sec. 80 %
plugin_git 2015-05-30 12:16:52 193 sec. 0 %
plugin_subversion 2016-08-03 13:26:06 78 sec. 0 %
rest-support 2016-11-23 07:14:57 33 sec. 80 %
webmaster-test-osee-dev 2016-11-11 16:22:34 882 sec. 0 %

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

Page generated by Alambic 3.2 on Tue Mar 28 02:08:29 2017.