modeling.emfcompare Plugin Hudson



Hudson Continuous Integration Engine

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

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

Metrics

The following metrics are available:

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

History

Failing Jobs

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

  • collaborative.modeling.mars-master-nightly has been failing for 117 days.
  • collaborative.modeling.neon-master-nightly has been failing for 117 days.
  • egit.logical-master-nightly has been failing for 183 days.
  • maintenance-3.2 has been failing for 17424 days.
  • maintenance-nightly has been failing for 315 days.
  • master-build-on-egit-logical-nighlty has been failing for 73 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
collaborative.modeling.mars-master-nightly 2017-09-10 03:00:59 207 sec. 0 %
collaborative.modeling.neon-master-nightly 2017-09-10 02:00:59 283 sec. 0 %
egit.logical-master-nightly 2017-09-15 00:01:53 73 sec. 0 %
maintenance-3.2 2017-06-27 02:01:04 455 sec. 0 %
maintenance-nightly 2017-06-26 23:01:04 1358 sec. 60 %
master-build-on-egit-logical-nighlty 2017-09-09 00:31:06 14 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
clean-nightly 2017-09-08 22:10:14 48 sec. 100 %
cli-master-gerrit 2015-05-22 06:03:06 265 sec. 100 %
master-extras-gerrit 2017-09-08 05:37:34 489 sec. 100 %
master-nightly 2017-09-08 22:01:07 525 sec. 80 %
master-performance 2017-09-09 02:01:07 1185 sec. 60 %
master-performance-git 2017-09-09 03:01:07 5675 sec. 60 %
master-performance-large 2017-09-09 04:01:07 1860 sec. 40 %
master-performance-large-git 2017-09-09 08:00:59 25846 sec. 60 %
master-quality 2017-09-08 20:01:07 744 sec. 53 %
publish-integration 2017-07-14 03:27:13 51 sec. 40 %
publish-milestone-manual 2017-09-12 05:02:49 11 sec. 100 %
publish-nightly 2017-09-08 22:09:57 12 sec. 100 %
sandbox 2014-10-23 04:17:00 10 sec. 100 %
shell_tests 2017-08-23 09:01:48 0 sec. 80 %
test-releng 2017-09-10 00:00:59 1535 sec. 100 %

Page generated by Alambic 3.3.2 on Fri Dec 15 01:11:17 2017.