Hi,
Are there particular reasons against having a larger history (number) of
jenkins builds (eg at [0])? Sometimes useful to go back more than 1-2 days..
If not, who could change this (I don't seem to have the karma)?
Cheers,
Stefan
--
[0] - https://builds.apache.org/job/sling-trunk-1.6/
On Tue, 2015-01-13 at 15:24 +0100, Stefan Egli wrote:
Hi,
Are there particular reasons against having a larger history (number) of
jenkins builds (eg at [0])? Sometimes useful to go back more than 1-2 days..
If not, who could change this (I don't seem to have the karma)?
Cheers,
Stefan
Hi Robert,
On 1/13/15 4:02 PM, Robert Munteanu romb...@apache.org wrote:
I guess it's limited to not overload Jenkins ( both memory and disk
space ) with history.
Do we know how much a build needs in terms of disk space? I would have
assumed that it keeps only the test/console results not the
On Tue, Jan 13, 2015 at 5:14 PM, Stefan Egli stefane...@apache.org wrote:
Hi Robert,
On 1/13/15 4:02 PM, Robert Munteanu romb...@apache.org wrote:
I guess it's limited to not overload Jenkins ( both memory and disk
space ) with history.
Do we know how much a build needs in terms of disk
