Service

ci.jenkins.io

Summary

As a developer trying to correlate flaky tests or build performance I have no visibility into the underlying infrastructure to correlate failures.

things like

1. did my test fail because the CPU was starved
2. was memory an issue (was I consuming 100% of available memory and thrashing the GC) (link to above)
3. are the memory limits applied to builds appropriate or not
4. could I get CI results faster if I ran more forks (surefire) for the given hardware
5. is the hardware even moderately sized (hint it is not), or what should that size be?

e.g. jenkinsci/jenkins#6236 (comment) and related discussion

Reproduction steps

1. run a build in CI (e.g. by creating a PR to a plugin or Jenkins core
2. try and see if there is CPU to spare to make it faster (or reduce the amount of CPU an agent needs)
3. try and see if there is memory to spare to make it faster (or reduce the amount of memory an agent needs)
4. try and correlate a test failure with resource constraints (at the time the test was running was the cpu resources at max capacity