modeling.emfcompare Plugin Jenkins



Jenkins Continuous Integration Engine

Jenkins instance [NA] is located at https://ci.eclipse.org/emfcompare/.

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

Metrics

The following metrics are available:

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

Failing Jobs

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

  • maintenance-3.2 has been failing for 18895 days.
  • master-build-on-egit-logical-nighlty has been failing for 730 days.
  • master-performance has been failing for 847 days.
  • master-performance-git has been failing for 847 days.
  • master-performance-large has been failing for 847 days.
  • master-performance-large-git has been failing for 832 days.
  • master-quality has been failing for 1351 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
maintenance-3.2 2021-09-17 06:00:10 21 sec. 0 %
master-build-on-egit-logical-nighlty 2021-07-21 02:00:10 43 sec. 0 %
master-performance 2021-07-24 06:00:26 17 sec. 0 %
master-performance-git 2021-07-24 07:00:25 22 sec. 0 %
master-performance-large 2021-07-24 08:00:26 12 sec. 0 %
master-performance-large-git 2021-09-18 12:00:20 22 sec. 0 %
master-quality 2021-07-21 00:00:27 19 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 2021-01-06 03:12:06 5 sec. 100 %
cli-master-gerrit 2015-05-22 10:03:06 265 sec. 100 %
maintenance-nightly 2016-11-04 16:32:48 691 sec. 100 %
master-extras-gerrit 2021-07-19 15:04:50 466 sec. 40 %
master-gerrit 2021-07-20 12:26:34 436 sec. 60 %
master-nightly 2021-07-20 12:31:52 757 sec. 100 %
publish-integration 2018-03-08 16:04:13 93 sec. 40 %
publish-milestone 2021-07-20 12:59:06 27 sec. 60 %
publish-release 2021-07-16 13:14:55 69 sec. 33 %
sandbox 2014-10-23 08:17:00 10 sec. 100 %
shell_tests 2020-01-14 10:36:43 0 sec. 80 %
test-releng-jiro 2021-02-23 16:14:37 31 sec. 100 %

Page generated by Alambic 3.3.3-dev on Sat Sep 25 12:53:52 2021.