| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Is it possible to use git submodules in repositories for releasing packages via bloom?
I used it in a package and it succeeded for the devel-build (even on Jenkins), but now the build seems to fail for the binarydeb-jobs because it can't find files from the submodule.
Thanks and best regards, Sebastian
I think you've answered the question yourself: it doesn't work.
Using git submodules requires extra submodule init and checkout steps that probably don't happen anywhere along the release pipeline.
Working with git submodules tends to be tricky and error-prone, and most of the developers I've met do their best to stay away from them.
Bloom is generally designed to import your codebase from your upstream repository, massage it to produce a git-buildpakage(GBP) repository for each version of Ubuntu you're releasing into, and make that repository available to the build farm.
If you're trying to use git submodules in the GBP repository, don't.
If your upstream repository uses submodules, you'll either have to extend bloom to support submodules, or release the submodules in your project directly.
I've bumped into the same problem and I think the behavior is still the same as three years ago. @Sebastian Kasperski, have you found another workaround?
Unfortunately not. I had to add my library-code (the previous sub-module) to the ros-package directly, which is not a nice solution at all.
I just stumbled upon this answer, it seems this is possible now, following the discussion on github.
Asked: 2014-05-21 22:00:17 -0600
Seen: 915 times
Last updated: May 14 '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.
