Jenkins doc build fails because of nested custom messages which are hosted in external, unreleased package
Some of our indexed packages fail to be built on the Jenkins documentation server. The problem seems to be that those packages define custom messages/services/actions which have nested custom messages of our message repo (asr_msgs) and that repo can't be found during the build process.
You can find an example of a failed build here (for the package asr_recognizer_prediction_ism). The other packages that fail share the same problem:
- asr_direct_search_manager
- asr_next_best_view
- asr_recognizer_prediction_psm
- asr_world_model
How can we fix this problem? Would it be sufficient to fully release the asr_msgs package so it will be available as a binary package and could be found by rosdep? Or is there some other way to provide the asr_msgs package to the documentation build process?
Suggestion: update the title to reflect the fact that these messages are hosted by packages that are unreleased.
"Nested custom messages" is probably not the problem.