From: Dan Kegel <dank@kegel.com>
To: Samuel Mi <samuel.miing@gmail.com>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
binutils@sourceware.org, gcc@gcc.gnu.org,
David Edelsohn <dje.gcc@gmail.com>,
Diego Novillo <dnovillo@google.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Automated Toolchain Building and Testing
Date: Thu, 29 Aug 2013 10:11:00 -0000 [thread overview]
Message-ID: <CAPF-yOYop0YNvOsKiFMSm3mA+Dzs-OCASvz0tJD2rKcgrNP57Q@mail.gmail.com> (raw)
In-Reply-To: <CAG3=hgt21iuJubCa+hjFSsT6C4gEBwwT1OdoY4XP1Zj53knrhA@mail.gmail.com>
On Wed, Aug 28, 2013 at 5:52 PM, Samuel Mi <samuel.miing@gmail.com> wrote:
>> This looks like a SSH connector for the Jenkins server side, no?
> No. Actually, Jenkins implements a built-in SSH server within itself.
Doesn't really help platforms that can boot linux but that don't have
a sufficient
version of Java/python. For them, one really wants a buildbot/jenkins/whatever
build node written in C/C++, since those are the languages most likely to be
universally available on such machines.
- Dan
next prev parent reply other threads:[~2013-08-29 1:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 10:03 Jan-Benedict Glaw
2013-08-28 10:39 ` Sebastian Huber
2013-08-28 21:26 ` Samuel Mi
2013-08-29 0:52 ` Jan-Benedict Glaw
2013-08-29 1:18 ` Samuel Mi
2013-08-29 7:23 ` Jan-Benedict Glaw
2013-08-29 10:02 ` Samuel Mi
2013-08-29 10:11 ` Dan Kegel [this message]
2013-08-29 10:23 ` Paul_Koning
2013-08-29 11:21 ` Jan-Benedict Glaw
2013-08-29 13:02 ` Rainer Orth
2013-08-29 14:33 ` Jan-Benedict Glaw
2013-08-29 22:40 ` Diego Novillo
2013-08-30 8:54 ` Jan-Benedict Glaw
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=CAPF-yOYop0YNvOsKiFMSm3mA+Dzs-OCASvz0tJD2rKcgrNP57Q@mail.gmail.com \
--to=dank@kegel.com \
--cc=binutils@sourceware.org \
--cc=dje.gcc@gmail.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jbglaw@lug-owl.de \
--cc=samuel.miing@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).