Set Up Continuous Integration
Continuous Integration validates your Objectives on every pull request. A deployment pipeline can also start Objectives on a robot after it installs a release.
The examples use GitHub Actions, but the patterns translate directly to GitLab, Jenkins, or any other CI host.
Continuous Integration
Reusable Workflows
We provide a reusable workflow for integration testing your robot configurations, running each Objective in a MoveIt Pro container in your CI pipeline. This ensures that your robot configurations are compatible with MoveIt Pro and that all Objectives are functioning as expected. To use this workflow in GitHub Actions:
jobs:
integration-test-in-moveit-pro-container:
uses: PickNikRobotics/moveit_pro_ci/.github/workflows/workspace_integration_test.yaml@v0.0.2
with:
image_tag: ${{ github.event_name == 'pull_request' && github.event.pull_request.base.ref || github.ref_name }}
colcon_test_args: "--executor sequential"
secrets: inherit
For the full workflow source, visit the MoveIt Pro CI GitHub repository.
Custom Actions
We provide a custom action for linting your Objectives in a robot configuration. This action ensures that your Objectives are properly formatted and adhere to best practices. Add this job to your workflow:
jobs:
validate_objectives:
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v5
- uses: PickNikRobotics/moveit_pro_lint@v0.0.1
For the full action source, visit the MoveIt Pro Lint GitHub repository.
Start Objectives from a deployment pipeline
A deployment pipeline that installs a MoveIt Pro release on a robot can start an Objective afterward by sending a goal to the /do_objective action from a ROS 2 client on the robot network. See Run an Existing Objective for an rclpy client and the ros2 action send_goal command line.