technology.collections Plugin Jenkins

Jenkins Continuous Integration Engine

Jenkins instance [NA] is located at

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


The following metrics are available:

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

Failing Jobs

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

  • deploy-p2-maven has been failing for 1814 days.
  • release_webmaster has been failing for 774 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
deploy-p2-maven 2019-05-04 21:54:51 61 sec. 0 %
release_webmaster 2020-06-30 10:57:22 1822 sec. 40 %

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
deploy 2022-07-05 14:59:17 562 sec. 100 %
gsc-ec-converter upload 2016-05-30 02:28:12 9 sec. 100 %
hipp-setting-analysis 2016-07-06 09:02:51 0 sec. 50 %
javadoc 2022-07-05 15:34:19 2007 sec. 100 %
master 2022-07-31 03:00:18 600 sec. 100 %
new-version 2022-07-06 15:34:19 555 sec. 80 %
publish-p2-repo 2022-07-05 15:12:08 206 sec. 100 %
release 2022-07-05 14:45:57 578 sec. 100 %
service-release 2020-08-20 20:41:07 506 sec. 60 %

Page generated by Alambic 3.3.3-dev on Sat Aug 13 08:26:26 2022.