From: Steve Simon <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] anyone using jenkins or hudson?
Date: Sat, 12 Nov 2016 09:07:52 +0000 [thread overview]
Message-ID: <615CEC82-26E0-417F-839F-C16C59714537@quintile.net> (raw)
hi
i put together a hudson/jenkins client which,
(because i had the framework to hand) i implemented
as a file system. currently it has been tested against
exactly one jenkins instance.
anyone willing to test against their build servers, i am particularly
interested in a hudson test.
-Steve
reply other threads:[~2016-11-12 9:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=615CEC82-26E0-417F-839F-C16C59714537@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).