Looking at https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/
the history is 30 builds for only one branch (same for others)
this history is consuming space

On Fri, 28 Dec 2018 at 19:58, Christofer Dutz <christofer.d...@c-ware.de>
wrote:

> Hi all,
>
> seeing PLC4X consuming 6 GB ... being a quite small project, that's
> clearly too much.
> Even if I have an idea why this is probably the reason. Could you please
> also share what's consuming that much space?
>
> Chris
>
>
>
> Am 27.12.18, 20:05 schrieb "Karl Heinz Marbaise" <khmarba...@gmx.de>:
>
>     Hi Chris,
>
>     On 27/12/18 19:27, Chris Lambertus wrote:
>     >
>     >
>     >> On Dec 27, 2018, at 4:36 AM, Karl Heinz Marbaise <khmarba...@gmx.de>
> wrote:
>     >>
>     >> Hi Gavin,
>     >>
>     >> On 27/12/18 13:00, Gavin McDonald wrote:
>     >>> On Thu, Dec 27, 2018 at 10:27 AM Karl Heinz Marbaise <
> khmarba...@gmx.de <mailto:khmarba...@gmx.de>> wrote:
>     >>>     <snip>
>     >>>     Furthermore I'm a little bit astonished that jobs consume
> space on
>     >>>     Master cause If I'm correct no job should run on Master...
>     >>> Right, they dont, but artifacts etc are stored there.
>     >>
>     >> Oups ? Which one ...Can you show a more detailed list in maven-box
> directory...? Maybe we can tweak the configuration a little bit to suppress
> storing artifacts there ? Sounds strange to me…
>     >
>     > As Robert mentioned, this is a multibranch build, so the actual
> artifacts are deep in the tree. Here is an example
>     >
>     > 
> root@jenkins02:/x1/jenkins/jenkins-home/jobs/maven-box/jobs/maven-surefire/branches/master/builds#
> du -sh *
>     > 416M      105
>     > 490M      106
>     > 419M      107
>     > 491M      108
>     > 16K       109
>     > 48K       110
>     > 499M      111
>     > 481M      112
>     > 515M      113
>     > 495M      114
>     >
>     > As you can see, there are 10 stored builds dating back to 15
> December. This could be adjusted to only store 5 builds or 7 days worth and
> reduce the usage of this particular branch/job by nearly 50%.
>     >
>     > Build 105 contains hundreds of log files, including one 48MB log, as
> well as zipped archives of what appear to be built releases. I can’t see a
> need for these to be kept, so perhaps your build could be adjusted to purge
> these:
>     >
>     >
> /x1/jenkins/jenkins-home/jobs/maven-box/jobs/maven-surefire/branches/master/builds/105/archive
>     >
>     > [ .. ]
>     > -rw-r----- 1 jenkins jenkins 20370694 Dec 15 06:47
> surefire-its--windows-jdk11-maven3.2.x.zip
>     > -rw-r----- 1 jenkins jenkins 20211112 Dec 15 06:54
> surefire-its--windows-jdk11-maven3.3.x.zip
>     > -rw-r----- 1 jenkins jenkins 20250674 Dec 15 07:00
> surefire-its--windows-jdk11-maven3.5.x.zip
>     > -rw-r----- 1 jenkins jenkins 17077193 Dec 15 06:52
> surefire-its--windows-jdk7-maven3.2.x.zip
>     >
>     >
>     > -Chris
>     >
>     >
>     >
>     >>
>     >> But let us investigate that...
>     >>
>
>     That is what I expected so there is room for improvement...
>
>     Thank Chris...
>
>     I will take a deeper look into this..
>
>     Kind regards
>     Karl Heinz Marbaise
>
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Reply via email to