ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
For documentation you can reference other repository names using the depends
entry (see REP 141). An example making use of this is multiwii.
For the devel jobs no such information exists. A devel job operates only on a single repository and installs all its dependencies from Debian packages. Since those are not available for L
it doesn't work for your repository N
. Therefore you might want to disable the devel job for repo N
for now which you can do by adding test_commits: false
to the source
entry (see an example).
A depends
entry could be added to source
blocks too. Then the devel
job would need to be a hybrid of the devel and prerelease process. We haven't implemented since its use is very limited. E.g. if you want to make correlated changes to L
and N
(e.g. change API and use the modified API) a pull request job would still fail. Simply because it uses the branch from one repo (e.g. N
) but not the one from L
. So you need a prerelease job to cover this case. If you on the other hand just commit the changes to L
without trying if N
actually works with it the failing CI job of N
is pretty late (and would e.g. not even be triggered if you don't commit to N
after committing the change to L
).
For adding a depends
entry for the source
block it would require an updated version of REP 143 (the successor of REP 141) as well as support from the buildfarm. If you see a need for this it would be great if you could work on PRs for this. I am happy to help in that process.