tools.cdt Plugin Jenkins



Jenkins Continuous Integration Engine

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

There are 51 jobs defined on this instance. 21 are green (stable), 2 are yellow (unstable), 3 are red (failing).

Metrics

The following metrics are available:

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

Failing Jobs

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

  • cdt-check-maven-plugin-updates has been failing for 65 days.
  • cdt-master-run-dash-licenses has been failing for 18654 days.
  • debug-tests-master-gdb-master has been failing for 138 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
cdt-check-maven-plugin-updates 2021-01-24 05:56:06 343 sec. 33 %
cdt-master-run-dash-licenses 2021-01-12 01:38:45 537 sec. 0 %
debug-tests-master-gdb-master 2021-01-21 08:58:00 1756 sec. 11 %

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
cdt-10.0 2021-01-24 08:49:00 3809 sec. 99 %
cdt-9.11 2021-01-22 08:01:00 4303 sec. 99 %

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
bug560283-test3 2020-05-26 02:31:32 40 sec. 100 %
bug560283-test4 2020-05-26 03:54:04 443 sec. 100 %
cdt-10.0-standalone-debugger 2020-09-10 16:17:56 508 sec. 100 %
cdt-10.1 2021-01-24 08:11:00 3798 sec. 100 %
cdt-10.1-standalone-debugger 2020-12-11 14:34:33 471 sec. 100 %
cdt-gdb-adapter-master 2021-01-20 23:19:08 150 sec. 100 %
cdt-gdb-adapter-verify 2021-01-05 09:33:22 131 sec. 60 %
cdt-gdb-vscode-master 2021-01-07 19:42:50 107 sec. 100 %
cdt-gdb-vscode-verify 2020-04-24 15:11:11 255 sec. 100 %
cdt-master 2021-01-24 08:19:00 4324 sec. 100 %
cdt-master-check-code-cleanliness 2021-01-24 08:00:00 669 sec. 80 %
cdt-master-standalone-debugger 2020-09-04 02:02:04 511 sec. 100 %
cdt-verify-code-cleanliness-pipeline 2021-01-26 16:07:01 629 sec. 80 %
cdt-verify-test-cdt-other-pipeline 2021-01-26 16:07:01 1852 sec. 100 %
cdt-verify-test-cdt-ui-only-pipeline 2021-01-26 16:07:01 1319 sec. 100 %
cdt-verify-test-dsf-gdb-only-pipeline 2021-01-19 14:19:32 1331 sec. 100 %
cdt-vscode-master 2021-01-07 12:41:39 83 sec. 100 %
cdt-vscode-verify 2019-05-03 15:29:13 136 sec. 100 %
debug-tests-master-gdb-8.3-branch 2021-01-25 08:52:00 1814 sec. 100 %
promote-a-build 2021-01-12 01:02:04 69 sec. 100 %
promote-files-to-download 2020-12-16 14:59:13 51 sec. 100 %

Page generated by Alambic 3.3.3-dev on Wed Jan 27 06:47:58 2021.