build.squeak.org slaves: which are there after all?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

build.squeak.org slaves: which are there after all?

Tobias Pape
Hi

I am looking around on our Jenkins CI and was puzzled that
there are several slave nodes (yay) but none of them
seem to have been alive for some time (nay…)




what can we do?

Best
        -Tobias


Bildschirmfoto 2015-03-31 um 20.26.49.PNG (93K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: build.squeak.org slaves: which are there after all?

David T. Lewis
> Hi
>
> I am looking around on our Jenkins CI and was puzzled that
> there are several slave nodes (yay) but none of them
> seem to have been alive for some time (nay…)
>
>
>
> what can we do?
>
> Best
> -Tobias
>

The first thing we should do:

Every job on the Jenkins CI should have a clear comment that says what it
is supposed to be doing, and who is responsible for it. Likewise for the
slave servers - if you cannot figure out what they are and who they belong
to, then they should not be there.

Dave



Reply | Threaded
Open this post in threaded view
|

Re: build.squeak.org slaves: which are there after all?

Edgar De Cleene
In reply to this post by Tobias Pape
Well, my Mac should be re configured to be a all time server.
Now it have a nice 4Tb disc what community could share.
Send mail private is needed and I glad setup.

Edgar





Reply | Threaded
Open this post in threaded view
|

Re: build.squeak.org slaves: which are there after all?

Frank Shearar-3
In reply to this post by David T. Lewis
On 31 March 2015 at 19:44, David T. Lewis <[hidden email]> wrote:

>> Hi
>>
>> I am looking around on our Jenkins CI and was puzzled that
>> there are several slave nodes (yay) but none of them
>> seem to have been alive for some time (nay…)
>>
>>
>>
>> what can we do?
>>
>> Best
>>       -Tobias
>>
>
> The first thing we should do:
>
> Every job on the Jenkins CI should have a clear comment that says what it
> is supposed to be doing, and who is responsible for it. Likewise for the
> slave servers - if you cannot figure out what they are and who they belong
> to, then they should not be there.

I mostly agree with the comment about the slaves. Mostly.

At any rate, andrad, havnor, norst and way are mine. I'll remove all
but norst, because they sadly no longer exist.

It's a pity Jenkins doesn't display the "title" of the node, or you'd
see that norst is "Frank's OS X box", wihich I consider to be
sufficiently informative :)

frank


> Dave
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: build.squeak.org slaves: which are there after all?

Frank Shearar-3
On 2 April 2015 at 13:33, Frank Shearar <[hidden email]> wrote:

> On 31 March 2015 at 19:44, David T. Lewis <[hidden email]> wrote:
>>> Hi
>>>
>>> I am looking around on our Jenkins CI and was puzzled that
>>> there are several slave nodes (yay) but none of them
>>> seem to have been alive for some time (nay…)
>>>
>>>
>>>
>>> what can we do?
>>>
>>> Best
>>>       -Tobias
>>>
>>
>> The first thing we should do:
>>
>> Every job on the Jenkins CI should have a clear comment that says what it
>> is supposed to be doing, and who is responsible for it. Likewise for the
>> slave servers - if you cannot figure out what they are and who they belong
>> to, then they should not be there.
>
> I mostly agree with the comment about the slaves. Mostly.
>
> At any rate, andrad, havnor, norst and way are mine. I'll remove all
> but norst, because they sadly no longer exist.
>
> It's a pity Jenkins doesn't display the "title" of the node, or you'd
> see that norst is "Frank's OS X box", wihich I consider to be
> sufficiently informative :)

Forgot to add: "lfp" is "least fixed point" is Tony Garnock-Jones.
I've pinged him.

"jgon" is Jeff Gonis. I've pinged him too.

You can find the "titles" of the nodes at URLs like
http://build.squeak.org/computer/norst/

frank

> frank
>
>
>> Dave
>>
>>
>>