turtlebot3-burger_150.png
turtlebot3-waffle-pi_150.png
turtlebot3-arm_150.png
walking-y2_150.png
turbot3-multi_150.png
turbot3-dl-ros1_150.png
turbot3-ai.png
turbot3-dl-ros2_150.png
turbot3-slam_150.png
turbot3-arm_150.png
turtlebot4-lite_150.png
turtlebot4-pro_150.png
turbot4-dl_150.png
turbot4-ai_150.png
aidriving-racebot_150.png
aidriving-autodrive_150.png
turtlebot-arm_150.png
openmanipulator-x_150.png
Home » PX4开发指南 » PX4开发指南-15.2.持续集成

PX4开发指南-15.2.持续集成

纠错,疑问,交流: 请进入讨论区请点击进入页面,扫码加入微信群或Q群进行交流

获取最新文章: 扫一扫加入“创客智造”公众号

PX4 Continuous Integration

  • PX4 builds and testing are spread out over multiple continuous integration services.

Travis-ci

  • Travis-ci is responsible for the official stable/beta/development binaries that are flashable through QGroundControl. It currently uses GCC 4.9.3 included in the docker image px4io/px4-dev-base and compiles px4fmu-{v1, v2, v4}, mindpx-v2, tap-v1 with makefile target qgc_firmware.

  • Travis-ci also has a MacOS posix sitl build which includes testing.

Semaphore

  • Semaphore is primarily used to compile changes for the Qualcomm Snapdragon platform, but also serves as a backup to Travis-ci using the the same px4io/px4-dev-base docker image. In addition to the set of firmware compiled by Travis-ci, Semaphore also builds for the stm32discovery, crazyflie, runs unit testing, and verifies code style.

CircleCI

  • CircleCI tests the proposed next version of GCC to be used for stable firmware releases using the docker image px4io/px4-dev-nuttx-gcc_next. It uses the makefile target quick_check which compiles px4fmu-v4_default, posix_sitl_default, runs testing, and verifies code style.

纠错,疑问,交流: 请进入讨论区请点击进入页面,扫码加入微信群或Q群进行交流

获取最新文章: 扫一扫加入“创客智造”公众号


标签: px4开发指南