Awesome, thanks Robert. And now . . .yet one more thing to read up on 
AH! Missed this bit . . .
To get cloud9 working on the ‘console’, you’d have to "sudo apt-get
install nodejs nodejs-legacy npm" however the cloud9 bit hasn’t been
packaged so you still have to do this part by hand:
Reading now, and enjoying the commentary.
I'm thinking the next step is publishing the build somewhere. Any suggestion
on how best to package it?make ARCH=arm KBUILD_DEBARCH=armhf LOCALVERSION=-git<version>
CROSS_COMPILE=<bin>/arm-linux-gnueabihf- KDEB_PKGVERSION=1cross
deb-pkg
Looks like this working now too!
dpkg-deb: building package
`linux-image-3.14.17-gitd88949624f5cbaaec41322a44bc3aa6807c40ed1:armhf'
in `../linux-image-3.14.17-gitd88949624f5cbaaec41322a44bc3aa6807c40ed1_1cross_armhf.deb'.
program finished with exit code 0
elapsedTime=152.038273
we should probably use:
git rev-parse --short HEAD
as that will return: d889496 instead of the full string.. 
Regards,
>>
>> I'm thinking the next step is publishing the build somewhere. Any
suggestion
>> on how best to package it?
>
> make ARCH=arm KBUILD_DEBARCH=armhf LOCALVERSION=-git<version>
> CROSS_COMPILE=<bin>/arm-linux-gnueabihf- KDEB_PKGVERSION=1cross
> deb-pkgLooks like this working now too!
dpkg-deb: building package
`linux-image-3.14.17-gitd88949624f5cbaaec41322a44bc3aa6807c40ed1:armhf'
in
`../linux-image-3.14.17-gitd88949624f5cbaaec41322a44bc3aa6807c40ed1_1cross_armhf.deb'.
program finished with exit code 0
elapsedTime=152.038273we should probably use:
git rev-parse --short HEAD
as that will return: d889496 instead of the full string..
OK. I've tried to also switch it to working off of github webhooks rather
than just polling the git repository. I had to upgrade buildbot to 0.8.9 to
handle the github webhooks.
The builds are currently being dropped into
http://builds.beagleboard.org/linux. I hope to manage to get URLs placed
into the build reports, but haven't quite gotten there.
>>
>> I'm thinking the next step is publishing the build somewhere. Any
suggestion
>> on how best to package it?
>
> make ARCH=arm KBUILD_DEBARCH=armhf LOCALVERSION=-git<version>
> CROSS_COMPILE=<bin>/arm-linux-gnueabihf- KDEB_PKGVERSION=1cross
> deb-pkgLooks like this working now too!
dpkg-deb: building package
`linux-image-3.14.17-gitd88949624f5cbaaec41322a44bc3aa6807c40ed1:armhf'
in
`../linux-image-3.14.17-gitd88949624f5cbaaec41322a44bc3aa6807c40ed1_1cross_armhf.deb'.
program finished with exit code 0
elapsedTime=152.038273we should probably use:
git rev-parse --short HEAD
as that will return: d889496 instead of the full string..
OK. I've tried to also switch it to working off of github webhooks rather
than just polling the git repository. I had to upgrade buildbot to 0.8.9 to
handle the github webhooks.
Still haven't been able to trigger builds properly off of pull requests
like the MachineKit folks do. Their config scripts are much more
complicated, which is why I've kinda had to figure it out a bit from
scratch.
I'll consider the buildbot deployed as soon as I can get this pull-request
functionality. As part of that, I'd want to add a master branch that
follows mainline and maintain a pull-request that will rebuild mainline
with a BeagleBone defconfig and whatever other minimal patches are needed
to make it boot, or perhaps it should just build omap2plus_defconfig per
your previous script recommendation?
The builds are currently being dropped into
http://builds.beagleboard.org/linux. I hope to manage to get URLs placed
into the build reports, but haven't quite gotten there.
As of build 25, URLs now get placed into the build results:
http://builds.beagleboard.org/builders/runtests/builds/25 links to
http://builds.beagleboard.org/linux/25.html. I'm sticking with the full
string for now as I am relying on buildbot to tell me the revision, rather
than fetching it directly using git.
I'll let these build up a bit before I worry about a rotation script.
As of build 25, URLs now get placed into the build results:
http://builds.beagleboard.org/builders/runtests/builds/25 links to
http://builds.beagleboard.org/linux/25.html. I'm sticking with the full
string for now as I am relying on buildbot to tell me the revision, rather
than fetching it directly using git.I'll let these build up a bit before I worry about a rotation script.
Looks good:
u-boot handled the really long name just fine.
Regards,