This repository has been archived by the owner on Nov 13, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 76
New Continuous Integration Method #309
Comments
@130s I'm mostly looking for your feedback |
This was referenced Jul 8, 2016
Merged
+1 Great job! |
The two places we currently needed this new CI method has been merged, so this issue is resolved for now. It would be nice if all moveit_* repos used this new script, but I don't think its critical at this moment to do so. In fact, I'd rather all those places just got merged into a single repo (future topic). Closing this issue. |
Closing this issue since there seems to be acceptance - @130s has started using this script in various places such as ros-interactive-manipulation/manipulation_msgs#8 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've created yet another continuous integration script - its a combination of the strengths of industrial_ci and the simplicity of @jbohren and my original MoveIt! travis script that was recently revitalized by @rhaschke. The show-stopper problem with the simple .travis.yml script is that it doesn't support ROS Kinetic, and I've been working hard to get the Kinetic code working so this is important.
The problem with the
industrial_ci
script are many:It is certainly possible to fix these things in industrial_ci, as I tried but the turn around time seemed kind of slow because changing anything in this script could potentially break many other projects in the ROS Industrial project using
industrial_ci
. @rhaschke came to the same conclusionI've addressed his issue by making the console output really pretty. This new script uses customized MoveIt! Docker containers.
So I propose creating a
moveit_ci
repo and moving my https://github.com/davetcoleman/moveit_ci project there. See the README in that project for more details on the script.This new script has solved building Kinetic for MoveIt!
The text was updated successfully, but these errors were encountered: