From: Samuel Mi <samuel.miing@gmail.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: 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:02:00 -0000 [thread overview]
Message-ID: <CAG3=hgt21iuJubCa+hjFSsT6C4gEBwwT1OdoY4XP1Zj53knrhA@mail.gmail.com> (raw)
In-Reply-To: <20130828185453.GF29134@lug-owl.de>
On Thu, Aug 29, 2013 at 2:54 AM, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> On Thu, 2013-08-29 02:43:54 +0800, Samuel Mi <samuel.miing@gmail.com> wrote:
>> > ...or can you, instead of using the Java-based
>> > client part of Jenkins, issue all commands over a SSH (or maybe even
>> > Telnet...) session? Is there a module for this available?
>> If making jenkins running on target systems you want whether old or
>> modern, then take a look at Jenkins-SSH
>> (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+SSH) to remotely
>> control over ssh.
>
> This looks like a SSH connector for the Jenkins server side, no?
No. Actually, Jenkins implements a built-in SSH server within itself.
At this point, it's consider to be a normal SSH server. So, you can
remotely access Jenkins server via SSH after setting up corresponding
configurations within it.
next prev parent reply other threads:[~2013-08-29 0:52 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 [this message]
2013-08-29 10:11 ` Dan Kegel
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='CAG3=hgt21iuJubCa+hjFSsT6C4gEBwwT1OdoY4XP1Zj53knrhA@mail.gmail.com' \
--to=samuel.miing@gmail.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 \
/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).