All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Brendan Higgins <brendanhiggins@google.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Valentin Rothberg <valentinrothberg@gmail.com>,
	Josh Triplett <josh@joshtriplett.org>,
	Scott Branden <scott.branden@broadcom.com>,
	Knut Omang <knut.omang@oracle.com>, Shuah Khan <shuah@kernel.org>,
	Matthew Wilcox <willy@infradead.org>
Subject: [ANN] kdevops - Linux kernel development devops framework
Date: Fri, 16 Aug 2019 08:08:56 +0000	[thread overview]
Message-ID: <20190816080856.GL16384@42.do-not-panic.com> (raw)

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

I'd like to announce my first release of kdevops [0] which I am happy to
share with the community. The goal behind this project is to provide a
modern devops framework for Linux kernel development. It is not a tests
suite, it is designed to *use* *any* test suites, and more importantly,
it allows us to let us *easily* set up test environments in a jiffie. It
supports different virtualization enviornments, and different cloud
environments, and supports different Operating Systems.

This is all built on top of ansible, vagrant and terraform. There's a
few demo projects which shows you how this can be used, one for fstests,
and another for selftests.

I've provided a bit more of details on my kernel blog [1]. Give it a
spin, and send rants / patches my way.

[0] https://github.com/mcgrof/kdevops/
[1] https://people.kernel.org/mcgrof/kdevops-a-devops-framework-for-linux-kernel-development

  Luis

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2019-08-16  8:09 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=20190816080856.GL16384@42.do-not-panic.com \
    --to=mcgrof@kernel.org \
    --cc=brendanhiggins@google.com \
    --cc=josh@joshtriplett.org \
    --cc=knut.omang@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=scott.branden@broadcom.com \
    --cc=shuah@kernel.org \
    --cc=valentinrothberg@gmail.com \
    --cc=willy@infradead.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 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.