Continuous Integration - rtbf64c

[Chris Johns]

Hello,

A long term goal of the RTEMS project is to support continuous 
integration. Continuous integrations takes patches and commits and 
builds and tests them providing public reporting of the results. Adding 
continuous integration to the project provides better turn around for 
changes that effect different architectures or BSPs lowering the work 
load on the RTEMS maintainers who have commit access. It allows 
different configurations to be tested that are often missed or nor done 
because of time and resource reasons, exposing any issues a patch may 
have when it goes in rather than some other point in time. The net 
effect is the improvement of the RTEMS code base as well as visible 
reporting of the current build state.

The first stage of this work was the conversion to git providing us with 
change sets. We are now starting on the next stage, bringing a buildbot 
server online. This stage will allow us to better examine the build 
system and configuration in RTEMS and to look at ways to improve its 
performance so we can get the best out of the infrastructure resources 
we have. In the future we will add a patch management tool which will 
allow better testing and reporting on specific patches.

The RTEMS server, rtbf64c, purchased to perform this task, will be taken 
off line in 48 hours time and reconfigured to support the continuous 
integration effort. If you have access to the machine and have anything 
you wish to keep please move it to another machine.

Any testing or tool building tasks that are not critical should look to 
using the other hardware we have available.

Thanks.
Chris