Embedded Linux Development Model With Jenkins
 

I am part of a small team ( 4 - 5 ) people working on an embedded linux project. We are using Buildroot and the Linaro toolchain to build for our target. We use git for version control and Jenkins for nightly builds.

This is our first go at a project like this and I've been unsuccessful at finding any resources describing models for development with this kind of environment.

Right now after a nightly build I create a tarball of the Buildroot 'output' directory, which contains the u-boot images and root file system. This can be downloaded directly from the Jenkins 'archive' page for the last successful build.

Some of us will be working on lower level development and some on user space development (QT). Our problem is deciding what is the most efficient / streamlined approach is to developing in an environment like this given that people will be working on different areas within the project scope. The userland guys could download the tarball with everything and incorporate their applications into the rfs to run on the board and debug, but how should we handle work done on the lower level development? Basically, how should we distribute the artifacts to the team? I greatly appreciate any thoughts.