Files
jenkins/war/resources/help/project-config/log-rotation.html
T
jglick 277539081b [FIXED HUDSON-2417] Taking stability into account when deciding which builds & artifacts to keep.
Previously, Hudson only tried to keep successful builds, meaning it would discard the last stable build
if there was a long run of unstable builds. This made .../lastStableBuild/... permalinks useless.
Artifact archiver logic with "latest only" also improved more generally:
1. Discards old artifacts at the start of the build. It might as well save the disk space sooner rather than later.
2. Rather than deleting all old artifacts prior to some point, now keeps the latest representatives
   of different stability classes of build: always keeps last stable if available, and also last successful if newer,
   and (just in case) also the last failed if that is newer. Formerly it behaved oddly: during a run of failed builds,
   all of their artifacts would be kept, though these are unlikely to be useful.
Also introducing tests for all this functionality, which does not seem to have been tested before.


git-svn-id: https://hudson.dev.java.net/svn/hudson/trunk/hudson/main@15587 71c3de6d-444a-0410-be80-ed276b4c234a
2009-02-23 04:57:45 +00:00

19 lines
765 B
HTML

<div>
This controls the disk consumption of Hudson by managing how long you'd like to keep
records of the builds (such as console output, build artifacts, and so on.)
Hudson offers two criteria:
<ol>
<li>
Driven by age. You can have Hudson delete a record if it reaches a certain age
(for example, 7 days old.)
<li>
Driven by number. You can have Hudson make sure that it only maintains up to
N build records. If a new build is started, the oldest record will
be simply removed.
</ol>
Hudson also allows you to mark an individual build as 'Keep this log forever', to
exclude certain important builds from being discarded automatically.
The last stable and last successful build are always kept as well.
</div>