-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update jsk_travis to 0.5.17 and fix travis #1288
Update jsk_travis to 0.5.17 and fix travis #1288
Conversation
|
jsk-ros-pkg/jsk_travis#410 simply cleanup travis result. I updatde jsk_recognition because at that time, I am working with that repository and having better travis output helps debugging. But unless you have any strong reason, you do not have to update .travis.yml settings just for this. This is the advanteage of using submodules, instead of cloning ci module everytime (https://github.com/ros-planning/moveit_ros/blob/kinetic-devel/.travis.yml#L21). updating jsk_travis in this PR seems nice to me. |
I preferred latter one because the out log is simpler and shorter. |
we need following PRs which are not released yet. ZebraDevs/fetch_ros#144 ZebraDevs/fetch_ros#146
Travis passed! |
Travis passed. |
jsk_travis
0.5.17
.travis.rosinstall.$ROS_DISTRO
fetch_ros
in.travis.rosinstall.$ROS_DISTRO
([fetch_navigation] add use_map_topic arg in fetch_nav.launch ZebraDevs/fetch_ros#144, [fetch_navigation] add launch_map_server argument in fetch_nav.launch ZebraDevs/fetch_ros#146)