modeling.mdt.ocl Plugin Jenkins



Jenkins Continuous Integration Engine

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

There are 27 jobs defined on this instance. 24 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): 27.
  • 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): 24.
  • 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 2022-07-20 18:08:34 1001 sec. 100 %
ocl-codegen-tests 2022-08-07 19:49:50 1425 sec. 50 %
ocl-compatibility-2018-09 2022-08-07 16:25:07 694 sec. 100 %
ocl-compatibility-2018-12 2022-08-07 17:43:10 698 sec. 100 %
ocl-compatibility-2019-03 2022-08-07 18:14:08 718 sec. 100 %
ocl-compatibility-2019-06 2022-08-07 19:55:07 860 sec. 100 %
ocl-compatibility-2019-09 2022-08-07 20:39:07 775 sec. 100 %
ocl-compatibility-2019-12 2022-08-07 21:53:07 712 sec. 100 %
ocl-compatibility-2020-03 2022-08-07 22:58:06 700 sec. 100 %
ocl-compatibility-2020-06 2022-08-07 23:19:07 690 sec. 100 %
ocl-compatibility-2020-09 2022-08-08 00:40:10 1309 sec. 100 %
ocl-compatibility-2020-12 2022-08-08 01:12:09 1307 sec. 100 %
ocl-compatibility-2021-03 2022-08-08 02:08:08 777 sec. 100 %
ocl-compatibility-2021-06 2022-08-08 02:25:08 765 sec. 100 %
ocl-compatibility-2021-09 2022-08-08 02:33:09 738 sec. 100 %
ocl-compatibility-2021-12 2022-08-08 02:53:07 767 sec. 100 %
ocl-compatibility-oxygen 2022-08-07 14:47:07 788 sec. 100 %
ocl-compatibility-photon 2022-08-07 15:57:07 704 sec. 100 %
ocl-ecore-standalone 2022-08-07 17:55:01 101 sec. 66 %
ocl-master 2022-08-07 17:34:54 1130 sec. 80 %
ocl-master-gerrit 2021-03-18 18:47:19 1067 sec. 100 %
ocl-uml-standalone 2022-08-07 19:47:10 127 sec. 50 %
promoter 2022-08-07 17:54:10 25 sec. 100 %
shell 2022-02-24 17:08:32 2 sec. 100 %

Page generated by Alambic 3.3.3-dev on Wed Aug 10 14:16:17 2022.