modeling.mdt.ocl Plugin Jenkins



Jenkins Continuous Integration Engine

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

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

Metrics

The following metrics are available:

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

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

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
ocl-branch-tests 2021-06-08 06:57:27 836 sec. 100 %
ocl-codegen-tests 2021-06-20 11:22:23 1091 sec. 100 %
ocl-compatibility-2018-09 2021-06-20 16:25:23 595 sec. 100 %
ocl-compatibility-2018-12 2021-06-20 17:43:23 754 sec. 100 %
ocl-compatibility-2019-03 2021-06-20 18:14:23 763 sec. 100 %
ocl-compatibility-2019-06 2021-06-20 19:55:25 589 sec. 100 %
ocl-compatibility-2019-09 2021-06-20 20:39:23 758 sec. 100 %
ocl-compatibility-2019-12 2021-06-20 21:53:22 574 sec. 100 %
ocl-compatibility-2020-03 2021-06-20 22:58:23 758 sec. 100 %
ocl-compatibility-2020-06 2021-06-20 23:19:23 584 sec. 100 %
ocl-compatibility-2020-09 2021-06-21 00:40:23 838 sec. 100 %
ocl-compatibility-2020-12 2021-06-21 01:12:22 866 sec. 100 %
ocl-compatibility-2021-03 2021-06-21 02:36:22 609 sec. 100 %
ocl-compatibility-oxygen 2021-06-20 14:47:22 580 sec. 100 %
ocl-compatibility-photon 2021-06-20 15:57:24 777 sec. 100 %
ocl-ecore-standalone 2021-06-20 09:07:23 93 sec. 100 %
ocl-master 2021-06-20 06:40:23 1354 sec. 100 %
ocl-master-gerrit 2021-03-18 18:47:19 1067 sec. 100 %
ocl-uml-standalone 2021-06-20 10:15:23 114 sec. 100 %
promoter 2021-06-20 07:03:23 26 sec. 100 %
shell 2021-06-17 09:05:14 20 sec. 100 %

Page generated by Alambic 3.3.3-dev on Thu Jun 24 12:18:49 2021.