tools.cdt Plugin Jenkins



Jenkins Continuous Integration Engine

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

There are 44 jobs defined on this instance. 18 are green (stable), 2 are yellow (unstable), 6 are red (failing).

Metrics

The following metrics are available:

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

Failing Jobs

There are 6 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-10.5 has been failing for 53 days.
  • cdt-9.11 has been failing for 72 days.
  • cdt-check-maven-plugin-updates has been failing for 193 days.
  • cdt-gdb-vscode-master has been failing for 72 days.
  • cdt-vscode-master has been failing for 324 days.
  • jonah-windows-test has been failing for 241 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
cdt-10.5 2022-01-23 08:44:00 120 sec. 60 %
cdt-9.11 2022-01-26 20:01:07 98 sec. 80 %
cdt-check-maven-plugin-updates 2022-01-26 08:56:00 337 sec. 25 %
cdt-gdb-vscode-master 2021-12-14 23:36:11 37 sec. 40 %
cdt-vscode-master 2021-12-14 23:12:11 43 sec. 0 %
jonah-windows-test 2021-05-31 13:19:14 215 sec. 0 %

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.2-java16 2021-04-11 02:42:40 4090 sec. 99 %
cdt-master-java16 2021-04-10 00:41:45 5342 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
cdt-gdb-adapter-master 2021-12-14 23:19:11 99 sec. 100 %
cdt-gdb-adapter-verify 2021-10-06 16:16:12 83 sec. 100 %
cdt-gdb-vscode-verify 2021-08-18 17:06:14 59 sec. 100 %
cdt-master 2022-01-26 23:19:07 5036 sec. 100 %
cdt-master-check-code-cleanliness 2022-01-26 23:00:07 603 sec. 100 %
cdt-master-jonah-test 2021-12-16 17:51:36 5224 sec. 40 %
cdt-master-run-dash-licenses 2021-12-01 17:59:38 626 sec. 100 %
cdt-verify-code-cleanliness-pipeline 2022-01-26 08:24:38 655 sec. 100 %
cdt-verify-terminal-only-pipeline 2022-01-12 23:57:31 810 sec. 100 %
cdt-verify-test-cdt-other-pipeline 2022-01-26 08:24:38 1314 sec. 100 %
cdt-verify-test-cdt-ui-only-pipeline 2022-01-26 08:24:38 1215 sec. 100 %
cdt-verify-test-dsf-gdb-only-pipeline 2022-01-26 10:47:10 2813 sec. 100 %
cdt-vscode-verify 2019-05-03 15:29:13 136 sec. 100 %
debug-tests-master-gdb-latest-branch 2022-01-21 08:26:04 3152 sec. 100 %
debug-tests-master-gdb-master 2022-01-20 08:58:00 3232 sec. 100 %
debug-tests-master-gdb-supported 2022-01-22 08:12:00 14363 sec. 100 %
promote-a-build 2022-01-13 02:14:44 74 sec. 100 %
promote-files-to-download 2021-12-08 15:01:15 62 sec. 80 %

Page generated by Alambic 3.3.3-dev on Thu Jan 27 17:32:57 2022.