tools.cdt Plugin Hudson



Hudson Continuous Integration Engine

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

There are 32 jobs defined on this instance. 19 are green (stable), 7 are yellow (unstable), 3 are red (failing).

Metrics

The following metrics are available:

  • Number of jobs defined on the host (JOBS): 32.
  • Number of jobs in status failed for more than one week (JOBS_FAILED_1W): 2.
  • Number of jobs in status green (JOBS_GREEN): 19.
  • Number of jobs in status yellow (JOBS_YELLOW): 7.
  • Number of jobs in status red (JOBS_RED): 3.

History

Failing Jobs

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

  • debug-tests-master-all-gdb-versions has been failing for 2 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.

  • cdt-sonar has been failing for 40 days.
  • kill-all-equinox-processes has been failing for 226 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
cdt-sonar 2017-03-23 02:01:02 2578 sec. 0 %
debug-tests-master-all-gdb-versions 2017-03-22 21:00:47 98 sec. 80 %
kill-all-equinox-processes 2017-02-09 08:59:45 1 sec. 66 %

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
cdt-8.8 2016-07-18 04:42:43 3519 sec. 99 %
cdt-9.1 2016-11-20 09:01:53 4383 sec. 99 %
debug-remote-tests-master-all-gdb-versions 2017-03-23 01:01:08 1319 sec. 15 %
debug-tests-master-gdb-7.12-branch 2017-03-23 03:00:47 1189 sec. 80 %
debug-tests-master-gdb-master 2017-03-23 04:00:47 1204 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
cdt-9.0 2016-09-08 05:00:48 3629 sec. 100 %
cdt-9.2 2017-03-06 17:05:48 3153 sec. 100 %
cdt-bugzilla-genie 2014-11-19 07:56:10 4 sec. 66 %
cdt-build-gerrit-patch 2017-02-13 17:29:26 3541 sec. 100 %
cdt-check-maven-plugin-updates 2017-03-19 00:00:47 419 sec. 100 %
Connect-doug-slave 2016-05-27 00:33:24 0 sec. 100 %
Connect-external-slave 2016-04-01 15:32:02 0 sec. 100 %
debug_manual_gdb_download 2016-10-11 11:26:48 198 sec. 100 %
delete-old-temp-files 2017-03-19 00:00:48 2 sec. 100 %
jstack-all 2017-02-15 22:42:21 2 sec. 100 %
launchbar-master 2017-02-22 20:00:53 111 sec. 80 %
launchbar-neon.1 2016-10-10 00:19:56 91 sec. 100 %
launchbar-verify 2017-02-22 08:54:51 146 sec. 100 %
Old Promote a build 2016-06-04 15:53:58 106 sec. 20 %
Promote a cdt build 2017-03-14 09:14:33 2 sec. 100 %
test 2017-02-16 10:44:30 0 sec. 100 %
tools-templates-1.0 2016-07-07 10:46:36 63 sec. 100 %
tools-templates-master 2017-02-14 08:01:28 55 sec. 100 %
tools-templates-verify 2017-02-14 04:28:20 75 sec. 100 %

Page generated by Alambic 3.2 on Thu Mar 23 20:00:16 2017.