This is the mail archive of the
mailing list for the binutils project.
Re: Automated Toolchain Building and Testing
- From: Samuel Mi <samuel dot miing at gmail dot com>
- To: Jan-Benedict Glaw <jbglaw at lug-owl dot de>
- Cc: binutils at sourceware dot org, gcc at gcc dot gnu dot org, David Edelsohn <dje dot gcc at gmail dot com>, Diego Novillo <dnovillo at google dot com>, Gerald Pfeifer <gerald at pfeifer dot com>
- Date: Thu, 29 Aug 2013 02:43:54 +0800
- Subject: Re: Automated Toolchain Building and Testing
- Authentication-results: sourceware.org; auth=none
- References: <20130827195417 dot GA29134 at lug-owl dot de> <CAG3=hgsX4vXg8tT8SQMr-=MjjN23LoKp5s5vfhRABxcR-j8ttA at mail dot gmail dot com> <20130828170259 dot GE29134 at lug-owl dot de>
> I'm not too sure if Jenkins is actually a good choice, just because I
> question that there's a working Java especially for old Unix-alike
> systems that GCC still (in theory) supports. What about eg. older IRIX
> or Ultrix systems?
I have no such experience on running jenkins under java runtime on old
and legacy systems. In my case, it's exactly focused on such
environment which is with modern linux-like systems like Ubuntu. plus,
the minimum runtime environment of running jenkins with up-to-date
version is java 1.5 or later.
> ...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.