From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: 'Stefan Beller' <sbeller@google.com>,
'Junio C Hamano' <gitster@pobox.com>,
git@vger.kernel.org, 'Joachim Schmitz' <jojo@schmitz-digital.de>
Subject: Re: Missed Commit in 2.20.1
Date: Thu, 27 Dec 2018 23:40:22 +0100 [thread overview]
Message-ID: <87pntmegq1.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <002401d49d07$325c7900$97156b00$@nexbridge.com>
On Wed, Dec 26 2018, Randall S. Becker wrote:
> Please stay tuned for patches. We are very much looking forward to having
> the two (or three) different NonStop hardware personalities supported
> without mods in the very near future. Our goal, assuming those patches are
> acceptable, is to move our build/test/distro into a Jenkins config that runs
> with minimal human involvement (a.k.a. me).
Portability patches like that are definitely wanted.
In case you haven't seen my recent work on getting GitLab CI up &
running check out
https://public-inbox.org/git/875zwm15k2.fsf@evledraar.gmail.com/
It differs from existing CI implementations for git.git in being focused
on doing the actual run on remote hosts that can be ssh'd to.
So perhaps you'd be interested in some of:
a) Contributing a NonStop box to the GCC Compile Farm
(https://cfarm.tetaneutral.net/machines/list/). Then I can add it to
my tests, but also other people porting free software will fix bugs
pro-actively before you spot them.
b) I now have a gitlab-runner I maintain powering this git-ci.git stuff
& presenting it on gitlab.com, if you give me SSH access I can add it
to my own runs...
c) ...or you can just run your own gitlab-runner on
https://gitlab.com/git-vcs/git-ci/ (although this amounts to giving
me ssh access, since you'll be running my code)....
d) ... or reuse the CI code I wrote to setup your own runner/pusher
against NonStop, only you'd have access to this....
e) Or do whatever you're planning with Jenkins.
If you want to just go with e) that's fine, just saying that you could
re-use some existing stuff with a-d) if you wanted.
next prev parent reply other threads:[~2018-12-27 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 22:20 GCC Compile farm (Linux, Solaris, AIX etc.) testing of git.git Ævar Arnfjörð Bjarmason
2018-12-26 10:38 ` Missed Commit in 2.20.1 Randall S. Becker
2018-12-27 22:40 ` Ævar Arnfjörð Bjarmason [this message]
2018-12-27 23:04 ` Randall S. Becker
2018-12-27 23:44 ` Ævar Arnfjörð Bjarmason
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=87pntmegq1.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jojo@schmitz-digital.de \
--cc=rsbecker@nexbridge.com \
--cc=sbeller@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.