Re: Automated Toolchain Building and Testing

[Jan-Benedict Glaw <jbglaw at lug-owl dot de>]

On Thu, 2013-08-29 01:18:32 +0000, Paul_Koning@Dell.com <Paul_Koning@Dell.com> wrote:
> On Aug 28, 2013, at 8:52 PM, Samuel Mi <samuel.miing@gmail.com> wrote:
> > 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.
> 
> What non-antique Linux doesn't come with Python?

GCC and Binutils don't exclusively run on Linux platforms. Actually,
the Linux targets are those which are actually tested the most by
usual day-to-day usage.  I'd specifically like to run tests on
platforms that are _not_ used by large user bases, but still supported
by GCC.

Those platforms tend to be non-Linux, non-i386, non-recent, or any
combination if those. *This* is what I want to support. (It still
should also run on Linux, though.)

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:                   ...und wenn Du denkst, es geht nicht mehr,
the second  :                          kommt irgendwo ein Lichtlein her.

Attachment: signature.asc
Description: Digital signature