Dear developers,
I was able to identify and exploit another saving potential: The repository
clones for the various Jenkins jobs.
I played around with the "Saros_Whiteboard" job. Normally, its workspace
consists of a Git clone (roughly 270 MByte) and a working copy (over 100 MByte,
including c
Hi Arsenij,
should be ok.
On 05.12.2013 12:06, Arsenij E Solovjev wrote:
> Hello everybody,
>
> The Jenkins Job that used up so much disk space was a weekly backup plugin.
> If no one has any objections, I will configure the plugin to only save
> the configuration of the jobs and not to backup th
Hello everybody,
The Jenkins Job that used up so much disk space was a weekly backup plugin.
If no one has any objections, I will configure the plugin to only save
the configuration of the jobs and not to backup the build results (which
was the main reason for disk space usage)
BR,
Arsenij
O
