Consider a way to turn off / turn on Jipp instances that are unused for long periods of time
https://ci.eclipse.org/egf/ seems to be relatively inactive. I suspect there are many, many such instances that are used very infrequently. I am only using it as an example.
As I look at CPU load, I see the EGF instance does take 15% CPU of one core from time to time, as Jenkins is running and it is reachable from the outside world. If we have 100 such instances, that are used infrequently, then we're wasting 15 CPU cores just having them idle - not including RAM and disk I/O.
It would be nice to have an automated mechanism that turns these instances "off". If we had #4380 then individuals on the project could start their own instance when they need it.
Such a mechanism does not exist. It would likely require some coding and some interfaces.
Activity
added Enhancement service:CBI service:jenkins labels
- There are some dormant JIPPs that need to be retired after getting approval from the projects.
- There are a few JIPPs that are used very infrequently due to low volume of commits or releases (e.g. some Jakarta EE JIPPs).
Instead of trying to shoehorn a start/restart functionality on top of the CI infrastructure, I'd recommend to rather spend time cleaning up the dormant JIPPs and coming up with a plan to get rid of Jenkins instances that just exist to build a project website or do signing.