tools.cdt.tcf Plugin Hudson



Hudson Continuous Integration Engine

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

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

Metrics

The following metrics are available:

  • Number of jobs defined on the host (JOBS): 21.
  • Number of jobs in status failed for more than one week (JOBS_FAILED_1W): 0.
  • Number of jobs in status green (JOBS_GREEN): 19.
  • Number of jobs in status yellow (JOBS_YELLOW): 2.
  • Number of jobs in status red (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
tcf-master-tests-4.6 2017-03-02 15:18:14 1089 sec. 80 %
tcf-master-tests-4.7 2017-03-02 15:28:34 1059 sec. 60 %

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
kill_agents 2015-06-08 04:09:30 0 sec. 80 %
ps_ef 2017-03-02 15:46:18 0 sec. 100 %
tcf-1.0 2015-02-13 09:01:12 236 sec. 50 %
tcf-1.1 2015-02-12 21:19:04 656 sec. 60 %
tcf-1.2 2015-02-12 21:18:29 608 sec. 100 %
tcf-1.3 2015-06-08 04:13:50 2167 sec. 100 %
tcf-1.4 2016-09-12 08:32:36 2011 sec. 100 %
tcf-1.4_WR_20160617_4.8.0_bugfix 2016-06-09 07:02:49 472 sec. 100 %
tcf-agent-x86Linux-1.3 2015-06-11 15:00:25 24 sec. 100 %
tcf-agent-x86Linux-master 2017-03-21 20:02:01 14 sec. 100 %
tcf-agent-x86Linux.gerrit 2016-10-21 06:16:28 16 sec. 100 %
tcf-master 2017-03-02 15:01:59 795 sec. 100 %
tcf-master-4.3 2017-03-02 15:17:41 805 sec. 100 %
tcf-master-4.4 2017-03-02 15:15:19 795 sec. 100 %
tcf-master-4.5 2017-03-02 15:02:48 904 sec. 100 %
tcf-master-4.6 2017-03-02 15:02:26 896 sec. 100 %
tcf-master-4.7 2017-03-02 15:02:48 920 sec. 100 %
tcf-master-tests 2017-03-02 15:17:52 1567 sec. 100 %
tcf.gerrit 2017-01-17 06:36:45 593 sec. 80 %

Page generated by Alambic 3.2 on Thu Mar 23 20:03:18 2017.