Bug 9726

Having various Yocto CROPS containers as build artifacts can provide some benefit. 1) it would provide greater visibility to the Yocto community that is used to using the AB, as opposed to Travis (where the containers are built now), 2) it would be nice to see the crops builds displayed on the waterfall page, along with the other items, 3) the free version of Travis has some limitations on the amount of resources you can use.

With that said, it is strongly preferred by the crops team that the AB parse the Travis yml file (included in the git repo) and use that as the sequence of steps, rather that having our own seperate AB file. IOW, build a conf file dynamically from the yml file, rather than having it hard coded. The yml file mostly just runs a set of shell scripts which in turn call docker to do the builds. The advantage to this is that now Travis and AB are building the same artifacts using the same source. Travis currently builds containers for all the processor types currently built on the AB, plus ready-to-run Ostro and Zephyr containers and we would want to do the same.