[GDB BuildBot] Upgrade & new URL (http://gdb-buildbot.osci.io)

[Sergio Durigan Junior <sergiodj at redhat dot com>]

Hi there,

I am writing to let you guys and gals know that I have just "flipped the
switch" and activated the new version of the GDB BuildBot.  A few things
have changed, so I thought I'd make this announcement on gdb-patches.

New machine (and new URL)
=========================

The awesome people at OSCI (Open Source Community Infrastructure --
<https://osci.io/>) have kindly donated a virtual machine in their
infrastructure so that I could run the BuildBot master on it.  My huge
thank you to them, especially to Lukas Berk (who first told me about
OSCI) and to Marc Dequènes (Duck), who set up the VM and helped me by
providing disk space to store the build results.

What this means is that I will not have to host BuildBot master on my
personal server anymore, but also (and more importantly), the URL has
changed.  The new URL is:

  http://gdb-buildbot.osci.io

BuildBot has been upgraded
==========================

Giving that I was going to have to move everything over to the new
machine, I took the opportunity and upgraded the BuildBot master.  We
were using version 0.8.14, a Python 2 version, pretty old and
unsupported by the upstream BuildBot community.  It took me *quite some
time* to upgrade all the scripts, but now we are on version 2.3.1, the
latest one.

For the "final user", the major change will be the UI, which has been
completely redesigned.  As with every major UI change, I found that some
people like it, and some people don't.  I will leave it to you to decide
:-).

For the people who provide the build machines ("slaves"), they will also
have to upgrade their BuildBot package to a version >= 0.9.  I have
already contacted all of the slave admins offlist and coordinated with
them; the majority have already upgraded their setups.

The URL to check the results follows the same standard:

  http://gdb-buildbot.osci.io/results/

As for the XFAILs, I stopped using git to store them; now, you can
access them directly here:

  http://gdb-buildbot.osci.io/xfails/

The rest should stay as-is: there will be e-mails to gdb-testers@ when
regressions are found, e-mails to gdb-patches@ and to the patch author
when a breakage happens, and e-mails to the patch author when a Try
Build is performed.

Note to Try Build users
=======================

Ah, that actually reminds me: speaking of Try Builds, if you are a Try
Build user, you will have to do a few things:

- Update your ~/.buildbot/options file and make sure you are using the
  new URL for the ssh service.

- Update your "buildbot" package, and make sure you are using a Python 3
  version of it.  Any version >= 0.9 should be enough.

- Probably apply a patch to be able to submit your Try Builds.  While
  doing tests here, I found a bug which prevented me from submitting the
  patch to be tested to master.  I had to hack my BuildBot installation.
  The patch can be found here:

     <https://bugzilla.redhat.com/show_bug.cgi?id=1661951#c9>

- If you are planning to submit a Try Build very soon, you will probably
  encounter some issues, because the buildslaves are still being
  migrated and not everything is available.  I would recommend you to
  either test things locally for now, or to take a look at the Workers
  page, check which builders are available, and tweak your
  ~/.buildbot/options file accordingly.  The page is:

     <http://gdb-buildbot.osci.io/#/workers>

Disclaimer
==========

Last, but definitely not least, I would like to say that even though I
have spent the last two weeks migrating everything and testing the setup
*a lot*, problems might still happen.  I understand it is annoying to
receive false-positive e-mails blaming your for a breakage, but please
be a bit patient.  I will keep two eyes on this during the next days,
and make sure that everything works.  Please let me know if there is
something broken.

Thank you.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/