Difference between revisions of "Builds"

From PaparazziUAV
Jump to: navigation, search
(Builds)
(Builds)
Line 1: Line 1:
 
= Builds =
 
= Builds =
  
The Paparazzi project has a dedicated [[build server|http://paparazzi.gondwana.com.au]] which is used to build Binary installers and do Continuous Integration (CI) builds of the code under development.
+
The Paparazzi project has a dedicated [http://paparazzi.gondwana.com.au build server] which is used to build Binary installers and do Continuous Integration (CI) builds of the code under development.
  
 
The server configuration and details on how to use it can be found on the [[Builds/Bamboo]] page.
 
The server configuration and details on how to use it can be found on the [[Builds/Bamboo]] page.

Revision as of 05:44, 6 March 2012

Builds

The Paparazzi project has a dedicated build server which is used to build Binary installers and do Continuous Integration (CI) builds of the code under development.

The server configuration and details on how to use it can be found on the Builds/Bamboo page.

Tests

Part of the reason for automating the build process is to check that the code in Paparazzi compiles. Another part is to test that the code that has been compiled actually works.

There are multiple levels to tests that can be performed as part of the build process.

  1. Compile the code and check that this works without error
  2. Compile the firmware for each target of the example aircraft configurations
  3. Compile the firmware for known hardware configurations, upload it and then run tests against the software running on the known hardware.

For more details of the testing see the tests page