Re: disk space on windows box

2012-05-23 Thread Niklas Gustavsson
On Wed, May 23, 2012 at 4:39 AM, Gavin McDonald wrote: > Also, there are numerous different java versions taking up ~3GB of space: > > harmony-5.0-jdk-32, ibm-java2-sdk-50-win-i386, ibm-java2-sdk-50-win-x86_64, > ibm-java-sdk-60-win-i386, ibm-java-sdk-60-win-x86_64, > ibm-sdk-j9wa64-142p-win64-amd

Re: disk space on windows box

2012-05-22 Thread Justin Mclean
Hi, > I'm looking into adding more space (need to add a disk etc.) Much appreciated. > Also, there are numerous different java versions taking up ~3GB of space. Sorry can't help there. We just need the standard 1.6 for the Flex SDK and 1.7 at some future point. Thanks, Justin

RE: disk space on windows box

2012-05-22 Thread Gavin McDonald
> -Original Message- > From: Justin Mclean [mailto:jus...@classsoftware.com] > Sent: Monday, 21 May 2012 5:43 PM > To: builds@apache.org > Subject: Re: disk space on windows box > > Hi, > > > I've clean out the Flex builds for now. But, we're lim

Re: disk space on windows box

2012-05-21 Thread Justin Mclean
Hi, > I've clean out the Flex builds for now. But, we're limited by the > current disk size on the Windows node Looks likes the windows build box has run out of disk space again but due to other jobs. > so please add a JIRA issue requesting additional space before adding back the > jobs :) Will

Re: disk space on windows box

2012-05-21 Thread Niklas Gustavsson
On Mon, May 21, 2012 at 1:02 AM, Justin Mclean wrote: > The Flex SDK is on the large size (2Gb all up) and I had created a second job > in order to run some check in tests. Eventually we would need several jobs. > > How do I view the amount of available free disk space on the windows build > mac

disk space on windows box

2012-05-20 Thread Justin Mclean
Hi, The windows1 build machine just run out of disk space due to a new new job I added. I've deleted the job so hopefully that's freed up the disk space and it's not caused too many issues. The Flex SDK is on the large size (2Gb all up) and I had created a second job in order to run some check