continuous integration
Posted: Sat Nov 30, 2013 11:49 pm
Current status: Jetkins is alive at http://crapcan-am.com:8080/
As ridiculous as this might sound, I think we need continuous integration - especially since we kinda have some unit tests (more on unit test in a separate thread)
What are our options? Since we are compiling for ARM does that mean we need a dedicated server somewhere to run our unusual GCC? Does anyone have a dedicated server? Does anyone have the time to setup continues integration?
One of the most mature free tools would be http://en.wikipedia.org/wiki/Jenkins_%28software%29
So the idea of this would be that each SVN commit triggers the invocation of 'make' for both 'firmware' and 'win32_algo_tests' (no the best name, they compile fine under linux) and ideally even execution of the 'tests' binary
The result of these actions is published on the web - either everything worked fine and we have 'green' status or something does not compile or does not pass tests and this puts us into the red zone.
As ridiculous as this might sound, I think we need continuous integration - especially since we kinda have some unit tests (more on unit test in a separate thread)
What are our options? Since we are compiling for ARM does that mean we need a dedicated server somewhere to run our unusual GCC? Does anyone have a dedicated server? Does anyone have the time to setup continues integration?
One of the most mature free tools would be http://en.wikipedia.org/wiki/Jenkins_%28software%29
So the idea of this would be that each SVN commit triggers the invocation of 'make' for both 'firmware' and 'win32_algo_tests' (no the best name, they compile fine under linux) and ideally even execution of the 'tests' binary
The result of these actions is published on the web - either everything worked fine and we have 'green' status or something does not compile or does not pass tests and this puts us into the red zone.