rtucker / bladerf-buildbot Goto Github PK

There is the ability to do manual builds, but automatic builds are still elusive.

Azure looks like a solid option for Windows service (imagine that), although their pricing is somewhat elusive... I spun a BASIC.A1 VM for the entire month and they somehow figured it was running for about 4 hours/day, thus billing me for ~114.9 hours ($8.50). Storage, data transfer, storage transactions, etc, were comparatively trivial. Total bill was $9.31, which was free due to the trial.

So, for an entire month of keeping a standing Windows VM going, I'd expect to pay somewhere between $9.31 or $55.86.

Also need to consider how to output the .exe files.

I've been pretty happy with Clang's ''scan-build'', especially considering that the Coverity scan rate-limit increased. Any chance we could get this baked into the nightly build process?

The general gist of what would need to be done is:

$ cd $PATH_TO_BLADERF/host/
$ mkdir clang_scan && cd clang_scan
$ cmake -DCMAKE_C_COMPILER=/usr/share/clang/scan-build/ccc-analyzer ../
$ /usr/share/clang/scan-build scan-build make

... beep boop beep ...

scan-build: 25 bugs found.
scan-build: Run 'scan-view /tmp/scan-build-2014-05-13-192806-4281-1' to examine bug reports.

From there, I believe the output in the aforementioned /tmp directory could be copied into the appropriate location. I believe everything in the reports are relative links, so no massaging should be necessary.

Add 'nocache' option to ./do_build to avoid using cache (i.e. apply Ubuntu updates)

Add 'killit' option to ./do_run to do the kill/rm stuff

I picked up a few more bugs when increasing scan-build's -maxloop option to 16. It looks like scan-build defaults to 4?

Perhaps the build-bot could run it with 100 if you want to get wild and crazy? It looks like 1000 causes it to take some time!

Might as well see how this goes