CI for demos
Similar to #154 (closed). We could consider adding CI for for the ROS packages and even the ROS demos. To test that at least nothing fails.
Maybe it would be a good idea to copy the structure of core
in wolf_ros_node
to call dependent packages pipelines?
TODOs:
-
docker images for 16.04, 18.04, 20.04 with ros and wolf depenencies (
wolf_deps_ros
) and also opencv (wolf_vision_deps_ros
) -
configure wolf_ros_node
gitlab-ci.yml
-
configure wolf_ros_gnss
gitlab-ci.yml
-
configure wolf_ros_laser
gitlab-ci.yml
-
configure wolf_ros_imu
gitlab-ci.yml
-
configure wolf_ros_apriltag
gitlab-ci.yml
Demos are pending of two things:
- How the rosbags should be downloaded from google drive (stored in a new repo in gitlab).
- How to catch errors from launch (now if it compiles, errors in launch time do not imply that the pipeline fails): NOT POSSIBLE
Demos:
-
configure wolf_demo_gnss_imu
gitlab-ci.yml
-
configure wolf_demo_imu2d
gitlab-ci.yml
-
configure wolf_demo_laser2d
gitlab-ci.yml
-
configure wolf_demo_apriltag_imu
gitlab-ci.yml
Detect when roslaunch fails:
Maybe we could do a workaround to detect when roslaunch fails. A bash script that launch and detects if "node died" is printed..? Consider this when implementing the script.