Rationalize days-kept for artifacts

[jamoore]

A recent review of the hudson "days-kept" & "builds-kept" settings showed a good deal of randomness in settings. Further, Petr pointed out that whereas previously there were several days of artifacts for the OMERO-merge-{stable,develop} builds, there are now only the latest.

A policy should be put in place for these and changes should really be discouraged on highly-used builds. The classes of artifact-settings I can think of are:

• No logs needed (This should be rare)
• No artifacts needed
• Artifacts needed for 1 week (?)

For all jobs other than the rare "No logs needed", I'd propose to use the Advanced settings of the artifact configuration so that we keep all history.

Review

Discard Old Builds Slicer - Days to keep artifacts
==================================================
---0---
OME-docs-internal
---1---
OmeroJava-integration-stable
---5---
BIOFORMATS-cpp-daily
BIOFORMATS-daily
BIOFORMATS-maven
BIOFORMATS-maven-stable
ITK4-weekly
OMERO-merge-deploy-develop
OMERO-merge-develop
OMERO-merge-develop-ice35
OMERO-merge-develop2
OMERO-merge-stable
OMERO-merge-stable-ice35
OMERO-stable-upgrade-green
OMERO-submods-develop
OMERO-submods-stable
OMERO-upgrade-red
PyTables
SCC-self-merge
SCC-unrebased-prs

## Many of these make sense. "Days to keep..." is useful for, "I want to access this job for the week so I can test it"


Discard Old Builds Slicer - Days to keep builds
==================================================
---1---
BIOFORMATS-sync
OME-sync-tags
OPENMICROSCOPY-sync
---3---
ICE-version

### Propose to move all of these to "Max # of builds to keep" (no history!)


Discard Old Builds Slicer - Max # of builds to keep
==================================================
---50---
Lots
---20---
ANALYSIS-OMERO-merge-stable-ice34
---10---
Lots!
---5---
OMERO-develop-autoimport
OMERO-stable-centos6
--2--
ANALYSIS-OMERO-src
BOOST-WIN64-VS2012
ICU-WIN64-VC2012
PYTHON3-WIN64-VS2012

### Propose to move all of these to "keep with artifacts".



Discard Old Builds Slicer - Max # of builds to keep with artifacts
==================================================
---1---
Lots
---3---
OmeroJava-broken-stable
OmeroPy-integration-stable
---5---
Several
---10---
Several

### Propose to reduce the variance in these

[sbesson]

First series of changes has been applied as of today

• all Days to keep builds thresholds have been moved to Max # of builds to keep as suggested
• there are four values for Max # of builds to keep with artifacts: Disabled, 1, 5 (1 week), 10 (2weeks)

[sbesson]

The following policies have been implemented across the board for all CI jobs:

• Days to keep artifacts, Days to keep builds, Max # of builds to keep are nowdisabled for all jobs. All jobs keep build logs indefinitely by default.
• All log rotation thresholds are now set as Max # of builds to keep with artifacts.

There are currently four thresholds used for discarding artifacts:

• 1: no artifact history is kept
• 5: artifacts are typically conserver for a week (e.g. merge jobs)
• 10: artifacts are typically conserved for 2 weeks
• 50: mostly Bio-Formats jobs
• Disabled: artifacts are kept undefinitely if any (e.g. most jobs under this category produce no artifact)

The list of thresholds used by jobs can be consulted at ​http://hudson.openmicroscopy.org.uk/slicing/artifactsbuilds/