From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder site back online
Date: Sat, 16 Nov 2013 22:36:32 +0100 [thread overview]
Message-ID: <20131116223632.462c6e60@skate> (raw)
Hello,
As many of you have noticed, the autobuild.buildroot.org web site has
been down for a number of days. It was hosted on a Virtual Private
Server that I have been using since 10+ years, but it was getting short
on disk space, was not very powerful, and more importantly, I did not
have access to the host machine, which means that whenever something
bad/wrong was happening, there was nothing I could do, except rely on
people who didn't always had enough time to take care of the issue in a
timely fashion.
Therefore, I have migrated the service to a dedicated server that I
own. I have direct access to the support team, I can reboot the server,
access the logs. And this server has more disk space (1 TB) and is much
more powerful than the previous one.
This new service is temporarily available at:
http://autobuild.humanoidz.org
The build results from the Free Electrons build server have already
started to flow into this new infrastructure.
There are a few things that remain to be done:
* Changing the autobuild.buildroot.org to point to this new server.
I've already asked Peter to do so.
* Changing the configuration of the build servers maintained by Peter
so that they send their results to the new infrastructure. I've also
asked Peter to do so.
* Re-add the daily e-mails to the new infrastructure. However, since I
couldn't access the old server to turn them off, the old server will
start sending them (empty probably when it goes up). So as soon as
I'll have access to the old server to turn it off, I will migrate
the daily e-mails to the new infrastructure.
* Import the history of build results. This also requires me to have
access to the old server and transfer all the results to the new
server. It might take a bit of time.
Sorry again for the noise. At least, the build results are back up,
which is the most important during this -rc cycle.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2013-11-16 21:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 21:36 Thomas Petazzoni [this message]
2013-11-17 8:03 ` [Buildroot] Autobuilder site back online Thomas De Schampheleire
2013-11-17 17:29 ` Yann E. MORIN
2013-11-17 17:50 ` Yann E. MORIN
2013-11-17 22:44 ` Thomas Petazzoni
2013-11-18 23:15 ` Arnout Vandecappelle
2013-11-18 23:30 ` Thomas Petazzoni
2013-11-20 11:45 ` Fatih Aşıcı
2013-11-20 12:30 ` Thomas Petazzoni
2013-11-17 17:58 ` Peter Korsgaard
2013-11-17 22:38 ` Thomas Petazzoni
2013-11-18 12:55 ` Arnout Vandecappelle
2013-11-18 12:59 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131116223632.462c6e60@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox