technology.paho Plugin Jenkins



Jenkins Continuous Integration Engine

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

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

Metrics

The following metrics are available:

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

Failing Jobs

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

  • paho-1.2-build has been failing for 891 days.
  • paho-c-master has been failing for 1392 days.
  • paho-golang-develop has been failing for 18756 days.
  • paho-java-build-verify has been failing for 299 days.
  • paho-java-dev-nightly has been failing for 299 days.
  • paho-java-dev-test has been failing for 852 days.
  • paho-java-master-package has been failing for 18756 days.
  • paho-java-master-release-02 has been failing for 298 days.
  • paho-javascript-dev has been failing for 1262 days.
  • paho-python-master has been failing for 2204 days.
  • paho.mqtt.android-dev-nightly has been failing for 1312 days.
  • paho.mqtt.android-master-mavenCentralRelease has been failing for 1556 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
paho-1.2-build 2018-11-29 14:50:59 20 sec. 0 %
paho-c-master 2018-04-05 14:03:58 4 sec. 80 %
paho-golang-develop 2014-12-04 16:16:24 0 sec. 0 %
paho-java-build-verify 2020-07-13 21:48:00 54 sec. 0 %
paho-java-dev-nightly 2020-12-11 05:05:08 104 sec. 60 %
paho-java-dev-test 2020-12-11 05:05:08 832 sec. 0 %
paho-java-master-package 2019-09-23 15:46:27 23 sec. 0 %
paho-java-master-release-02 2020-07-17 03:11:41 21 sec. 80 %
paho-javascript-dev 2019-06-05 04:10:06 12 sec. 0 %
paho-python-master 2021-05-08 06:49:26 22 sec. 0 %
paho.mqtt.android-dev-nightly 2020-06-06 04:20:08 58 sec. 0 %
paho.mqtt.android-master-mavenCentralRelease 2017-02-03 10:31:50 45 sec. 20 %

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
AndroidNightlyFixTest 2016-10-10 14:19:27 11 sec. 25 %
paho-c-develop 2017-07-17 10:00:42 239 sec. 75 %
paho-java-experimental 2020-07-13 22:38:22 39 sec. 100 %
paho-java-master-release-01 2020-07-17 03:07:45 114 sec. 40 %
paho-java-master-release-03 2020-07-14 13:19:23 29 sec. 80 %
paho-java-master-test 2017-03-20 09:15:46 718 sec. 100 %
paho-javascript-master 2018-07-24 10:50:28 43 sec. 40 %
paho.mqtt.android-master-release 2017-01-24 15:32:06 728 sec. 40 %

Page generated by Alambic 3.3.3-dev on Sun May 9 07:27:29 2021.