| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Repository A contains a a.rosinstall file that contains it's source dependencies.
Within a.rosinstall there is:
BCIt happens that B also contains a rosinstall file, b.rosinstall that has repository D inside.
Is there a way with wstool to merge recursively so that every indirect dependency of A (E) is also cloned?
No, that is not one of the use-cases that wstool covers.
Repositories are almost completely opaque to wstool, it doesn't really understand anything about them (it essentially 'forwards' commands to vcs binaries that do all the work) and doesn't introspect the repositories that it clones.
It also (somewhat) follows the KISS principle: what you want could be done using a bash one-liner.
But it would also seem to result in nested .git (or other vcs) checkouts, which is not really something recommended.
It's not exactly what you are looking for, but vcstool's import verb does support git submodules:
--recursive Recurse into submodules (default: False)
and supports importing .rosinstall files.
Personally I don't like submodules at all, but it could provide an alternative approach.
Then I'll make my own script! It's for ros_gitlab_ci
Example bash function here. Be careful because this function deletes the rosinstall files along the way, only use in CI environment!
At the time I switched to GitLab industrial_ci was not compatible with GitLab CI. I like to be able to modify it on my own without waiting for someone to merge a request (usually takes weeks..). I could probably switch to industrial_ci but it would take a lot of time. And I would probably have
to re-implement some features that are missing in industrial_ci. Like being able to clone private repositories from GitLab using CI job tokens. industrial_ci uses SSH keys and the setup is MUCH more complicated.
I still think ros_gitlab_ci is simpler than industrial_ci
Asked: 2019-02-05 09:34:02 -0500
Seen: 974 times
Last updated: Feb 05 '19
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
