From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: [BuildBot] News and announcements
Date: Fri, 19 Jun 2015 19:05:00 -0000 [thread overview]
Message-ID: <87h9q3ldsk.fsf@sergiodj.net> (raw)
In-Reply-To: <86fv5orqd0.fsf@gmail.com> (Yao Qi's message of "Fri, 19 Jun 2015 10:37:15 +0100")
On Friday, June 19 2015, Yao Qi wrote:
> Sergio Durigan Junior <sergiodj@sergiodj.net> writes:
>
>> Needless to say, we also welcome donations of new machines for our
>> BuildBot! For example, we don't have an ARM buildslave yet, which would
>> be very nice. So if you're interested in helping us, you can either
>> take a look at this wiki page:
>>
>> <https://sourceware.org/gdb/wiki/BuildBot>
>
> Hi Sergio,
> Does buildmaster need to access to buildslave? Is it OK that the
> buildslave is put behind the firewall? I'd like to know how these
> arm or aarch64 buildslaves are used in BuildBot, and see how to provide
> them from linaro or arm (and whether it is allowed to do so).
Hey Yao,
The buildslave is responsible for starting the connection, so the
buildmaster does not need to have direct access to it. I myself run a
buildslave behind a firewall/NAT, and there is no problem. All you need
to do is to set up the buildslave (as described in the wiki), tell me
about it (so that I can include it on buildmaster and generate a
password for you), and then start it.
The buildmaster will issue build requests to the buildslave, which will
build, run the tests, and the report back to buildmaster. That's it.
Nobody needs to have access to the buildslaves.
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-06-19 19:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87616mmcks.fsf@sergiodj.net>
2015-06-17 20:37 ` Simon Marchi
2015-06-17 21:58 ` Sergio Durigan Junior
2015-06-17 22:10 ` Doug Evans
2015-06-19 19:01 ` Sergio Durigan Junior
[not found] ` <86fv5orqd0.fsf@gmail.com>
2015-06-19 19:05 ` Sergio Durigan Junior [this message]
2015-06-21 7:02 David Edelsohn
2015-06-21 22:56 ` David Edelsohn
2015-06-22 19:05 ` Sergio Durigan Junior
2015-06-22 19:50 ` Sergio Durigan Junior
2015-06-23 1:18 ` Sergio Durigan Junior
2015-06-23 1:32 ` David Edelsohn
2015-06-23 1:44 ` Sergio Durigan Junior
2015-06-23 1:51 ` David Edelsohn
2015-06-23 2:11 ` Sergio Durigan Junior
2015-06-23 2:13 ` David Edelsohn
2015-06-23 2:26 ` Sergio Durigan Junior
2015-06-23 4:20 ` David Edelsohn
2015-06-23 4:37 ` David Edelsohn
2015-06-23 20:11 ` Sergio Durigan Junior
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=87h9q3ldsk.fsf@sergiodj.net \
--to=sergiodj@sergiodj.net \
--cc=gdb@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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