I know the recent Hudson versions does not keep everything
in memory like the old pre-jenkins versions did.
As far as I know it only keeps basic job information and
maybe recent build in memory but history and other rarely
accessed parts are left on disk.
My question is related to how a plugin developer can take
advantage of this functionality.
* What can I in a plugin do to ensure my information is
kept in memory if it is an often used piece of information (to
avoid heavy disk i/o)
* What can I in a plugin do to let my information be
evicted from memory ?
* Once a piece of information is retrieved from disk, how
long does it stay in memory and what is the eviction policy?