[jenkins_scripts] How to resolve source dependencies in our own ROS-Jenkins?
Hi,
I'm setting up a ROS build farm (we have a number of private repo that we want to test, too; release will will still be submitted via rosdistro). I'm following all the instructions in http://wiki.ros.org/buildfarm and have forked jenkins_tools into https://github.com/marc-hanheide/jenk... to deploy devel jobs to the jenkins instance. This is all working like a charm, but a problem I can't get my head round is how to resolve source dependencies when submitting "Development Tests" (see http://wiki.ros.org/regression_tests#... ). The problem is that we have repositories that depend on other not yet released repos (i.e. there are no .deb packages generated for them that could be resolved via rosdep ). What I'd expect for the devel script in https://github.com/ros-infrastructure... to do is to provide a mechanism to resolve those dependencies as well, but I found now way to solve this with the tools provided. Am I missing something here?
Summarised: How to build a repository in a Jenkins "Development Test" against other repositories that are also not yet released as debian packages?
Anyone has an idea?
Thanks,
Marc
