Publish results of OpenEmbedded builds

[Marcin Juszkiewicz]

I have few OpenEmbedded based builds on Jenkins and few new ones will be added in next months. They use standard way of publishing results and with last ones I got files sent.

But there is no way of accessing those results.

I would need structure like that:

/openembedded/oe-image-linaro-lamp/
/openembedded/oe-core-image-lsb-sdk/
/openembedded/sources/
/openembedded/sstate-cache/

First two are rootfs builds, third one will be populated with sources used by all OE builds (to comply with licenses requirements) and also may be used as mirror for builds. Last one contains build results which will be used by incremental builds.

Sources will take few GB, sstate cache will be 20+ gigabytes. Why keeping all those gigabytes? Few reasons:

1. Sources also contain git/svn/etc checkouts so we do not have to pull them from upstream. Shorter build time, more friendly to outside world.
2. By providing sources we comply to licenses.
3. Sstate cache will cut incremental builds to just build new items. In best situation most of build would be fetching sstate files and unpacking them instead of building.

Each Jenkins job will have 3 publish steps:

1. /openembedded/${JOBNAME}/ with build results (kernel + image)
2. /openembedded/sources/
3. /openembedded/sstate-cache/

Steps 2/3 would have lot of already uploaded data so rsync would be better then scp.

[Fathi Boudra (fboudra)]

OE LAMP job is fixed. I reused Ubuntu job types (ubuntu-images) and renamed the job to fill publish_to_snapshots script requirements.

As a side effect, path is more consistent with Ubuntu published images:
http://snapshots.linaro.org/openembedded/images/lamp/13/

It's following the naming scheme:
/openembedded/images/${JOBNAME}/${BUILDNUMBER}/

[Fathi Boudra (fboudra)]

OE sources/sstate-cache support is added to publish_to_snapshots script.
Tested successfully on openembedded-fetch-and-publish-test since build 14:
https://ci.linaro.org/jenkins/job/openembedded-fetch-and-publish-test/14/console

Closing the bug. All use cases should be covered.