Removal of spark buildbot

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Removal of spark buildbot

Gavin McDonald
HI All,

https://ci.apache.org/builders/serf-sparc64-solaris shows pending jobs since last August and the previous 
build that actually ran was July last year.

From what I can tell, the buildbot vm has been offline for over 5 months now.

Unless it will be revived, I intend to remove the node from our master, and remove the associated jobs from the subversion.conf file
in the next few days.

Thanks

Gavin McDonald (ASF Infra).


Reply | Threaded
Open this post in threaded view
|

Re: Removal of spark buildbot

Philip Martin
Gavin McDonald <[hidden email]> writes:

> https://ci.apache.org/builders/serf-sparc64-solaris
> <https://ci.apache.org/builders/serf-sparc64-solaris> shows pending
> jobs since last August and the previous
> build that actually ran was July last year.
>
> From what I can tell, the buildbot vm has been offline for over 5 months now.
>
> Unless it will be revived, I intend to remove the node from our
> master, and remove the associated jobs from the subversion.conf file
> in the next few days.

Yes, do so.  WANdisco did attempt to revive the buildbot after I left
but I believe the hardware has failed.


--
Philip
Reply | Threaded
Open this post in threaded view
|

Re: Removal of spark buildbot

Stefan Sperling-9
On Wed, Jan 10, 2018 at 02:56:51AM +0000, Philip Martin wrote:

> Gavin McDonald <[hidden email]> writes:
>
> > https://ci.apache.org/builders/serf-sparc64-solaris
> > <https://ci.apache.org/builders/serf-sparc64-solaris> shows pending
> > jobs since last August and the previous
> > build that actually ran was July last year.
> >
> > From what I can tell, the buildbot vm has been offline for over 5 months now.
> >
> > Unless it will be revived, I intend to remove the node from our
> > master, and remove the associated jobs from the subversion.conf file
> > in the next few days.
>
> Yes, do so.  WANdisco did attempt to revive the buildbot after I left
> but I believe the hardware has failed.

I am currently setting up a new OpenBSD/sparc64 buildbot.
I'll send more info once I've got it completely set up.
Reply | Threaded
Open this post in threaded view
|

Re: Removal of spark buildbot

Gavin McDonald


> On 10 Jan 2018, at 9:18 pm, Stefan Sperling <[hidden email]> wrote:
>
> On Wed, Jan 10, 2018 at 02:56:51AM +0000, Philip Martin wrote:
>> Gavin McDonald <[hidden email]> writes:
>>
>>> https://ci.apache.org/builders/serf-sparc64-solaris
>>> <https://ci.apache.org/builders/serf-sparc64-solaris> shows pending
>>> jobs since last August and the previous
>>> build that actually ran was July last year.
>>>
>>> From what I can tell, the buildbot vm has been offline for over 5 months now.
>>>
>>> Unless it will be revived, I intend to remove the node from our
>>> master, and remove the associated jobs from the subversion.conf file
>>> in the next few days.
>>
>> Yes, do so.  WANdisco did attempt to revive the buildbot after I left
>> but I believe the hardware has failed.
>
> I am currently setting up a new OpenBSD/sparc64 buildbot.
> I'll send more info once I've got it completely set up.

Good news!

In the meantime this sparc box and config have been removed.

Will be glad to assist in getting the new one attached to our master.

Thanks

Gav…


Reply | Threaded
Open this post in threaded view
|

Re: Removal of spark buildbot

Stefan Sperling-9
On Wed, Jan 10, 2018 at 09:23:49PM +1100, Gavin McDonald wrote:

> > On 10 Jan 2018, at 9:18 pm, Stefan Sperling <[hidden email]> wrote:
> > I am currently setting up a new OpenBSD/sparc64 buildbot.
> > I'll send more info once I've got it completely set up.
>
> Good news!
>
> In the meantime this sparc box and config have been removed.
>
> Will be glad to assist in getting the new one attached to our master.
>
> Thanks
>
> Gav…

Hey Gavin,

I am almost ready to connect my new bot.
Just now doing another test build after tweaking my scripts at
https://svn.apache.org/repos/asf/subversion/trunk/tools/buildbot/slaves/bb-openbsd

I've lost the buildslave password. Can you tell me what I could do to
view the password or to get it changed?

I suppose the final step would be to re-enable bb-openbsd in our slave config?
Since I can access that file in SVN so I could do that myself, I guess.

Thanks,
Stefan
Reply | Threaded
Open this post in threaded view
|

Re: Removal of spark buildbot

Doug Robinson
Stefan, et. al.:

Strangely, searching for Solaris brought this to my attention (I didn't see it before today).  Do you still need a Spark/Solaris box for testing?  I'm not sure what we've got but I can try to see if we've replaced the dead machine (yet) and whether you could use it?

Cheers.

Doug

On Wed, Jan 10, 2018 at 9:27 AM, Stefan Sperling <[hidden email]> wrote:
On Wed, Jan 10, 2018 at 09:23:49PM +1100, Gavin McDonald wrote:
> > On 10 Jan 2018, at 9:18 pm, Stefan Sperling <[hidden email]> wrote:
> > I am currently setting up a new OpenBSD/sparc64 buildbot.
> > I'll send more info once I've got it completely set up.
>
> Good news!
>
> In the meantime this sparc box and config have been removed.
>
> Will be glad to assist in getting the new one attached to our master.
>
> Thanks
>
> Gav…

Hey Gavin,

I am almost ready to connect my new bot.
Just now doing another test build after tweaking my scripts at
https://svn.apache.org/repos/asf/subversion/trunk/tools/buildbot/slaves/bb-openbsd

I've lost the buildslave password. Can you tell me what I could do to
view the password or to get it changed?

I suppose the final step would be to re-enable bb-openbsd in our slave config?
Since I can access that file in SVN so I could do that myself, I guess.

Thanks,
Stefan



--
DOUGLAS B ROBINSON SENIOR PRODUCT MANAGER

The LIVE DATA Company
Find out more wandisco.com

THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE PRIVILEGED

If this message was misdirected, WANdisco, Inc. and its subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. If you are not the intended recipient, please notify us immediately and destroy the message without disclosing its contents to anyone. Any distribution, use or copying of this email or the information it contains by other than an intended recipient is unauthorized. The views and opinions expressed in this email message are the author's own and may not reflect the views and opinions of WANdisco, unless the author is authorized by WANdisco to express such views or opinions on its behalf. All email sent to or from this address is subject to electronic storage and review by WANdisco. Although WANdisco operates anti-virus programs, it does not accept responsibility for any damage whatsoever caused by viruses being passed.