ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

Build failed in Jenkins debian branches

asked 2015-12-21 06:02:03 -0500

Andre Araujo gravatar image

Few days ago i have started the indexing process of our repository in ROS, as well as releasing some packages. Meanwhile i start receiving build erros from jenkins, it seems to be some version issues or a missing debian branches.

When i ran the bloom release, the only complain during the process are some dependencies in the packages. For example, the iai_kinect2, but i had ignored this errors and continuing with the release. Can this cause the missing debian branches in the realese repo and the consequently cause the erros when the jenkins build it?

<== Failed Could not resolve rosdep key 'iai_kinect2' Failed to resolve iai_kinect2 on ubuntu:saucy with: Error running generator: Failed to resolve rosdep key 'iai_kinect2', aborting.

Started by user Internal
Building remotely on in workspace <>
Fetching changes from the remote Git repository
Fetching upstream changes from git://
Checking out Revision 526731d6448065ff1c85e0192ea03e41e692abe1 (origin/master)
[ros-indigo-forte-rc-teleop_sourcedeb] $ /bin/bash /tmp/
# rosdistro.get_release_build_files() has been deprecated and its functionality is now handled by the 'ros_buildfarm.config' module
Cloning into 'forte_rc_robot-release'...
Branch upstream set up to track remote branch upstream from origin.
<>: No such file or directory
package name forte_rc_teleop version 1.0.4-0
+ cd <> && gbp-clone
Fetching targets
+ cd <> && git tag -l debian/*
No matching tag found. Are you sure you pointed to the right repository or the version is right?, expected debian/ros-indigo-forte-rc-teleop_1.0.4-0_saucy:
No tag; bailing
+ cd <> && git tag -l debian/*
No matching tag found. Are you sure you pointed to the right repository or the version is right?, expected debian/ros-indigo-forte-rc-teleop_1.0.4-0_trusty:
No tag; bailing
+ cd /tmp/ && ssh -- rm -rf /tmp/upload/ros-indigo-forte-rc-teleop
+ cd /tmp/n set: && ssh -- mkdir -p /tmp/upload/ros-indigo-forte-rc-teleop
+ cd /tmp/ && scp -r <>
Failed uploading for distro trusty: Command '['scp', '-r', '<',> '']' returned non-zero exit status 1
Errors have occurred in the source build see above.
Build step 'Execute shell' marked build as failure
Build step 'Groovy Postbuild' marked build as failure
Description set:
edit retag flag offensive close merge delete


Please consider to add more tags to your question to reach more users.

Dirk Thomas gravatar image Dirk Thomas  ( 2015-12-22 06:53:47 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2015-12-22 06:52:46 -0500

Dirk Thomas gravatar image

updated 2015-12-22 06:53:09 -0500

Yes, failing to resolve the necessary dependencies might result in not being able to generate the Debian specific branches. Please try to add the missing dependencies to rosdep and redo the bloom release.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2015-12-21 06:02:03 -0500

Seen: 98 times

Last updated: Dec 22 '15