| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
What is the process that defines what OSs the build farm builds packages for?
Example: In kinetic, cartographer is available for Ubuntu Default but cartographer is not available for Debian Jessie.
There doesn't seem to be any magic flags in the rosdistro entry.
Note: cartographer is just an example, I care more about the actual process.
I'll take a shot at an answer, although I expect @nuclearsandwich will weigh in later.
Blacklisting is done in the ros_buildfarm_config repo (production branch in this case). Not in the rosdistro. For cartographer specifically, see ros-infrastructure/ros_buildfarm_config#110. Reason given for blacklisting that package on Jessie:
cartographer's dependency
libceres-devdoesnt exist on Debian Jessie and we don't plan to backport it as Jessie is almost EOL
The complete blacklist for Jessie is maintained here. See REP-137: Specification/Release build file for the spec on the blacklist.
In general Bloom generates release artefacts for all supported configured target platforms (generators here). As @nuclearsandwich writes:
The release artifacts bloom generates are determined by the
actionsfield of each track in tracks.yaml. If you wish to change what is generated you can modify that list of commands.
Afaik you cannot ask Bloom to not generate for something. Blacklisting is done afterwards.
The release artifacts bloom generates are determined by the actions field of each track in tracks.yaml. If you wish to change what is generated you can modify that list of commands. However, if your release repo is public it is nice to generate the info so others can build packages you may not.
@gvdhoorn covered the salient points excellently. I have very little to add. :)
Asked: 2018-04-12 18:15:54 -0500
Seen: 146 times
Last updated: Apr 13 '18
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.
