public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Samuel Mi <samuel.miing@gmail.com>
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 00:52:00 -0000	[thread overview]
Message-ID: <20130828170259.GE29134@lug-owl.de> (raw)
In-Reply-To: <CAG3=hgsX4vXg8tT8SQMr-=MjjN23LoKp5s5vfhRABxcR-j8ttA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

On Wed, 2013-08-28 23:26:29 +0800, Samuel Mi <samuel.miing@gmail.com> wrote:
> Looks like you for now have been trying to find out a solution
> suitable for you to automatically build GCC from source combined with
> certain continuous systems like Jenkins. As a matter of fact, Jenkins
> is exactly a good choice to do such thing just mentioned, due to
> itself with so many plugins[1] you can pick up to fit your needs.

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?  ...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?

We've been using Jenkins at the company I work for, though only for
up-to-date mainstream systems with current state-of-the-art software.
But what I really like is to also support old and legacy systems, as
well as probably current ones with only a minimal userbase.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:                     Eine Freie Meinung in einem Freien Kopf
the second  :                   für einen Freien Staat voll Freier Bürger.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-08-28 17:03 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 [this message]
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
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=20130828170259.GE29134@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=binutils@sourceware.org \
    --cc=dje.gcc@gmail.com \
    --cc=dnovillo@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --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).