Thanks Maheshika for the prompt response!
On Wed, Sep 10, 2014 at 10:41 AM, Maheshika Goonetilleke mahesh...@wso2.com
wrote:
Hi Harsha Prabath
We are in the process of increasing the disk space.
Hi Rumesh
Most Jenkins builds have failed due to inadequate disk space.
Therefore,
Are the build logs, artifacts etc. cleaned from time to time, if not, we
will run into issues.
On Wed, Sep 10, 2014 at 10:41 AM, Maheshika Goonetilleke mahesh...@wso2.com
wrote:
Hi Harsha Prabath
We are in the process of increasing the disk space.
Hi Rumesh
Most Jenkins builds have
Why does workspace takes too much space? Is it because of the archived old
builds?
On Wed, Sep 10, 2014 at 10:24 AM, Maheshika Goonetilleke mahesh...@wso2.com
wrote:
Hi Azeez
Yes, the build has been configured to Discard old builds and artifacts.
According to the Disk Usage report,
Hi Kasun,
Yes, the workspace does include .m2.
Sample .m2 repo sizes;
product-greg : 13GB
product-as: 17GB
product-esb : 16GB
prodcut-ss: 14GB
product-dss : 16GB
product-is : 5.4GB
product-cep : 9.2GB
On Wed, Sep 10, 2014 at 4:00 PM, Kasun Gajasinghe kas...@wso2.com
Hi Kasun
Deleted all the directories in the repository. (
-Dmaven.repo.local=/build/jenkins-home/workspace/product-as/.repository)
Maven repo cleaner plugin have been already installed globally. However, I
think you need to add # or cron to schedule it.
[1]
On Wed, Sep 10, 2014 at 6:48 PM, Kasun Gajasinghe kas...@wso2.com wrote:
Given the bandwidth involved, cleaning up the repos in intervals of 7 days
is good? @Azeez/Sagara, any thoughts?
How long does it take to fill up the disk? If it takes 3 weeks, for
example, on average, we should cleanup
On Wed, Sep 10, 2014 at 4:15 PM, Afkham Azeez az...@wso2.com wrote:
On Wed, Sep 10, 2014 at 6:48 PM, Kasun Gajasinghe kas...@wso2.com wrote:
Given the bandwidth involved, cleaning up the repos in intervals of 7
days is good? @Azeez/Sagara, any thoughts?
How long does it take to fill up
Hi Maheshika,
It looks like we're still running into this issue in the builder machine.
Would you be able to have a look?
Cheers,
Prabath
On Wed, Sep 10, 2014 at 3:16 AM, cbuil...@wso2.org wrote:
See https://wso2.org/jenkins/job/product-ss/74/
--
Hi Maheshika,
This is occurs time to time. It says no space left on the device. This is
the reason for the previous build failure too. As I remember day before
yesterday, build was successful.
Thanks,
Harsha
On Wed, Sep 10, 2014 at 9:57 AM, Prabath Abeysekera praba...@wso2.com
wrote:
Hi
Hi Harsha Prabath
We are in the process of increasing the disk space.
Hi Rumesh
Most Jenkins builds have failed due to inadequate disk space.
Therefore, please increase the Jenkins disk space.
On Wed, Sep 10, 2014 at 10:32 AM, Harsha Kumara hars...@wso2.com wrote:
Hi Maheshika,
This is
10 matches
Mail list logo
