Box-Admins February 2013

box-admins@lists.squeakfoundation.org

5 participants
4 discussions

Increasing disk usage on box3 (build.squeak.org)
by Ken Causey 27 Feb '13

27 Feb '13

This is just a heads up that I'm noticing that the available disk space on box3 (aka build.squeak.org) is rather quickly decreasing. I'm still monitoring this and can't give a hard figure about how quickly it is decreasing yet. Of course it has always been understood that build.squeak.org is the primary focus of that system and that over time additional build tasks would be added resulting in increased usage of the system including disk space. But, and I will admit I'm not paying a lot of attention, I'm not aware of a lot of additional tasks yet. Please feel free to correct me on this. So, first I'm going to continue to monitor this for a few days at least at which point I can perhaps be more specific. Secondly, I for one would really appreciate if the admins of build.squeak.org would occasionally report on the status of build.squeak.org regarding added tasks/jobs/whatever. I understand that most of the discussion occurs on squeak-dev, and that's fine, just a very brief report with pointers for more info to posts on squeak-dev would be perfectly acceptable. Thirdly, is it possible there is some cleanup task that is not taking place? /var/lib/jenkins/workspace is at the moment 7.2GB (out of 12GB used on the server) and was 7.0GB yesterday. Ken

2 2

build.squeak.org
by Bert Freudenberg 15 Feb '13

15 Feb '13

On 2013-02-14, at 14:17, "David T. Lewis" <lewis(a)mail.msen.com> wrote: > On Thu, Feb 14, 2013 at 07:31:32AM +0000, Frank Shearar wrote: >> >> On 14 February 2013 01:18, David T. Lewis <lewis(a)mail.msen.com> wrote: >>> >>> By the way if anyone wants to work with this, you can find pre-traced 64-bit >>> images at http://squeakci.org/job/Squeak%2064-bit%20image/. >> >> *cough* http://build.squeak.org/job/Squeak%2064-bit%20image/ *cough* >> > > Oops, sorry. This is only about the 10th time I've forgotten that, I'll see > if I can do better next time ;) > > Dave Can we add a redirect, so that if some request goes to squeakci.org it gets redirected to build.squeak.org? That way people copying the URL from the browser will get the new one. - Bert -

2 2

Re: [squeak-dev] Release 4.4?
by Ken Causey 05 Feb '13

05 Feb '13

On 02/04/2013 02:21 AM, Frank Shearar wrote: > On 4 February 2013 00:52, Colin Putney<colin(a)wiresong.com> wrote: >> >> >> >> On Sun, Feb 3, 2013 at 12:01 PM, Frank Shearar<frank.shearar(a)gmail.com> >> wrote: >> >>> >>> >>> Hm, first I've heard of that. Where is it? >>> >> >> http://ftp.squeak.org/current_stable/ > > OK, I've flagged it as an issue with box-admins, and added an entry to > the release process at http://wiki.squeak.org/squeak/6189 > > frank > OK, the summation here is that only root or the owner of the directory (website is going to be able to 'update' a symbolic link within said directory. This is not something I had previously fully appreciated and so my setting the owner of these links to updates does not help users who can access the updates account despite the appearances, sorry about that. Basically there is no way to modify an existing symbolic link, to change it you have to remove and recreate it. So if you don't have write access to the directory, even if you have write access to the link, you are out of luck. I fixed the current_development and current_stable links. I also went ahead and created a 4.5alpha directory. Ken

4 4

Re: [squeak-dev] Release 4.4?
by Frank Shearar 04 Feb '13

04 Feb '13

On 4 February 2013 00:52, Colin Putney <colin(a)wiresong.com> wrote: > > > > On Sun, Feb 3, 2013 at 12:01 PM, Frank Shearar <frank.shearar(a)gmail.com> > wrote: > >> >> >> Hm, first I've heard of that. Where is it? >> > > http://ftp.squeak.org/current_stable/ I hadn't known about these guys. current_stable now points to 4.4. I would make current_development point to 4.5alpha but the updates user can't make directories in /var/www/files/. Oh, I see ln is being tricky. current_stable remains unchanged, pointing to 4.3, because it has decided to change the owner of the file but not update the link (presumably because updates doesn't have permission: updates@box2:/var/www/files$ ln -s 4.4 test ln: creating symbolic link `test' to `4.4': Permission denied So, what I need is this: * a new directory 4.5alpha (I'm just following the existing convention; I don't see massive value in a separate alpha dir, but I won't fight) * current_stable -> 4.4 * current_development -> 4.5alpha trunk points to current_development so shouldn't need updating. frank

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Box-Admins February 2013