From: akuster808 <akuster808@gmail.com>
To: Konrad Scherer <Konrad.Scherer@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: Wind River Continuous Integration project
Date: Fri, 20 Oct 2017 14:44:14 -0700 [thread overview]
Message-ID: <b8ea045d-6f65-1e91-75f2-5b39619e899b@gmail.com> (raw)
In-Reply-To: <c9dc44be-45fc-71b7-c488-d7b02e8beebf@windriver.com>
Konrad,
On 10/20/2017 11:18 AM, Konrad Scherer wrote:
>
> One of the common challenges of Yocto development is the setup and
> maintenance of a build cluster. If only there was a generic open
> source Yocto continuous integration project to make the setup and
> maintenance of build clusters easy...
>
> I have a working prototype and it's on GitHub.
>
> https://github.com/WindRiver-OpenSourceLabs/ci-scripts
>
> It is a set of scripts and docker images for building Yocto images
> using Jenkins and Docker. There are three main features that I think
> you will find interesting:
>
> 1) Multi-host builds using Docker Swarm. This provides an easy way to
> scale the build cluster from one to tens of machines. Docker Swarm
> makes this surprisingly simple.
>
> 2) Developer builds. This enables build testing of patches before they
> are committed to the main branches. It leverages the WR setup[1]
> program and a temporary layerindex to assemble a custom project that
> matches the developer's local project.
>
> 3) Toaster integration. A simple UI to dynamically expose the Toaster
> interface of all in progress builds.
>
> We are deploying this internally at Wind River and I hope that the
> oe-core community will be interested in collaborating on its development.
Thanks, I will have to play with it. This may help stable branch
maintenance.
- Armin
>
> Please have a look and give it a try. All feedback welcome!
>
> [1]: https://github.com/Wind-River/wr-lx-setup
>
next prev parent reply other threads:[~2017-10-20 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 18:18 Wind River Continuous Integration project Konrad Scherer
2017-10-20 21:44 ` akuster808 [this message]
2017-10-20 22:07 ` Randy MacLeod
2017-10-21 13:44 ` Tom Rini
2017-10-20 23:31 ` Yang, Lei
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=b8ea045d-6f65-1e91-75f2-5b39619e899b@gmail.com \
--to=akuster808@gmail.com \
--cc=Konrad.Scherer@windriver.com \
--cc=openembedded-core@lists.openembedded.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.