technology.ease Plugin Jenkins



Jenkins Continuous Integration Engine

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

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

Metrics

The following metrics are available:

  • Number of jobs defined on the host (CI_JOBS): 25.
  • 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): 1.
  • 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.

  • ease.maintenance.downloadarea has been failing for 443 days.
  • ease.verify.core.target.oxygen has been failing for 191 days.

List of failing jobs, sorted by last successful build.

Failing jobs
Name Last Build Last Duration Stability
ease.maintenance.downloadarea 2021-03-26 10:13:40 46 sec. 33 %
ease.verify.core.target.2020-06 2022-01-21 09:31:00 405 sec. 80 %
ease.verify.core.target.oxygen 2022-01-24 22:39:00 508 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
ease.verify.p2.sites 2022-01-26 16:46:00 34 sec. 71 %

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
ease.build.core 2022-01-26 04:21:59 627 sec. 100 %
ease.build.core.repopulate_nightly_p2_site 2021-10-15 13:25:52 640 sec. 100 %
ease.build.module.doclet 2022-01-26 04:21:15 44 sec. 100 %
ease.build.modules 2022-01-26 04:32:26 228 sec. 100 %
ease.build.nightly 2022-01-26 04:21:00 947 sec. 100 %
ease.build.release 2021-05-11 11:45:27 2516 sec. 60 %
ease.build.release.deploy 2021-06-22 06:41:37 69 sec. 100 %
ease.verify.core.gerrit 2022-01-18 19:17:07 676 sec. 40 %
ease.verify.core.target.2018-09 2022-01-26 18:31:00 541 sec. 100 %
ease.verify.core.target.2018-12 2022-01-22 04:36:00 557 sec. 100 %
ease.verify.core.target.2019-03 2022-01-22 22:35:00 549 sec. 100 %
ease.verify.core.target.2019-06 2022-01-25 14:29:00 616 sec. 80 %
ease.verify.core.target.2019-09 2022-01-26 03:06:00 542 sec. 100 %
ease.verify.core.target.2019-12 2022-01-22 11:36:00 562 sec. 100 %
ease.verify.core.target.2020-03 2022-01-22 01:28:00 604 sec. 100 %
ease.verify.core.target.2020-09 2022-01-25 03:27:00 536 sec. 100 %
ease.verify.core.target.2021-06 2022-01-20 19:09:00 534 sec. 80 %
ease.verify.core.target.photon 2022-01-25 02:08:00 560 sec. 80 %
ease.verify.modules.gerrit 2021-11-26 13:32:08 461 sec. 60 %
python.test 2019-05-23 12:34:46 490 sec. 66 %

Page generated by Alambic 3.3.3-dev on Thu Jan 27 17:58:33 2022.