public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: don.brown@codethink.com (Don Brown)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Update on CIP Testing Platform using KernelCI and LAVA
Date: Wed, 15 Feb 2017 17:37:45 -0500	[thread overview]
Message-ID: <6a99d98d9167de5bd7ab2230071a380a@codethink.com> (raw)


Hi Everyone,

I am writing to give you an update on where we stand with the Civil 
Infrastructure Platform (CIP).

As many of you know, we are using KernelCI for the Continuous 
Integration component and LAVA v2 for the kernel Testing platform. 
KernelCI performs the kernel builds against specific configurations and 
can verify boots and SOC's as well. LAVA provides the testing framework 
& infrastructure. Both come with complete results reporting to document 
what went wrong in the build, deployment or testing portion with a great 
level of granularity.

Where We Stand:
We have successfully merged the KernelCI VM and the LAVA Server VM into 
a single Virtual Machine.[1] We have KernelCI creating builds of the CIP 
Kernel [2] and we have LAVA running health-check tests in qemu. We are 
very close to having the health-check running on the Beaglebone Black, 
but we've had some trouble getting it communicating properly.

We expect to release the platform as a Beta version for the Embedded 
Linux Conference. The two original tutorials have been merged into one 
and can be found on the CIP Wiki.[3]


Links:

[1] CIP Testing Platform (Board-at-Desk-Single-Developer): 
https://gitlab.com/cip-project/board-at-desk-single-dev

[2] The CIP Kernel: https://gitlab.com/cip-project/linux-cip

[3] Tutorial: Board-at-Desk-Single-Developer KernelCI & LAVA VM Setup & 
Configuration: 
https://wiki.linuxfoundation.org/civilinfrastructureplatform/testinglavav2vmsetup


-- 
Don Brown
Codethink, Ltd.
Software Engineering Consultant
Indianapolis, IN USA
Email: don.brown at codethink.co.uk
Mobile: +1 317-560-0513

                 reply	other threads:[~2017-02-15 22:37 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=6a99d98d9167de5bd7ab2230071a380a@codethink.com \
    --to=don.brown@codethink.com \
    --cc=cip-dev@lists.cip-project.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