Revision history [back]

For the first quiestion about index.yaml, you cannot have duplicate entries in the dict. You would want to have myproject-jade or something like that to differentiate your packages from the mainline ones. Note that to extend jade you should add to the list of distribution files not add a new entry.

For the reprepro_config's your location is fine. They just need to be consistent enough for you

You don't have to use a custom rosdep database. That's only necessary if you want to be able to support injecting your own non-ros packages as dependencies.

The custom rosdistro paths should be dealt with on the buildfarm from the config files. That should only require customization for the end users/ non-buildfarm machines.

The repo machine should be running and connected to the jenkins instance as a slave named building_repository so that it can execute all the jobs. You should review the deployment docs to make sure you have all 3 types of machines deployed correctly: https://github.com/ros-infrastructure/buildfarm_deployment

Note creating a separable questions is usually more effective on this forum. (If there are related questions cross linking can help give context, but try to keep them self contained) I've tried to answer as much as I can but iterating it back and forth between a list of questions and a list of answers can be hard to follow when reading later.

For the first quiestion about index.yaml, you cannot have duplicate entries in the dict. You would want to have myproject-jade or something like that to differentiate your packages from the mainline ones. Note that to extend jade you should add to the list of distribution files not add a new entry.

For the reprepro_config's your location is fine. They just need to be consistent enough for you

You don't have to use a custom rosdep database. That's only necessary if you want to be able to support injecting your own non-ros packages as dependencies.

The custom rosdistro paths should be dealt with on the buildfarm from the config files. That should only require customization for the end users/ non-buildfarm machines.

The repo machine should be running and connected to the jenkins instance as a slave named building_repository so that it can execute all the jobs. You should review the deployment docs to make sure you have all 3 types of machines deployed correctly: https://github.com/ros-infrastructure/buildfarm_deployment

We haven't fully defined the overlay term. docs for addon and rosdep rules can be found here: https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/custom_rosdistro.rst

Note creating a separable questions is usually more effective on this forum. (If there are related questions cross linking can help give context, but try to keep them self contained) I've tried to answer as much as I can but iterating it back and forth between a list of questions and a list of answers can be hard to follow when reading later.