From: Bryan Schumaker <bjschuma@netapp.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Jenkins NFS CI
Date: Mon, 11 Apr 2011 16:52:03 -0400 [thread overview]
Message-ID: <4DA369F3.4020603@netapp.com> (raw)
Hi everybody!
I have posted my initial jenkins CI setup to a git repo located at: git://git.linux-nfs.org/projects/bjschuma/jenkins-nfs.git. I would appreciate feedback for making it both more useful and usable. I have it configured to test client changes, I haven't given much thought for testing the server.
You can find instructions for setting it up here: https://wiki.linux-nfs.org/wiki/index.php/Jenkins_CI and also in the README.txt I placed in the root of the git tree.
I have also created pre-configured virtual machine images that can be used with libvirt for running the tests. You can download them from http://linux-nfs.org/~bjschuma/jenkins_master.32.img and http://linux-nfs.org/~bjschuma/jenkins_master.64.img.
Thanks for any feedback!
- Bryan
reply other threads:[~2011-04-11 20:52 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=4DA369F3.4020603@netapp.com \
--to=bjschuma@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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).