shaun-edwards
commented
10 years ago Looks like the install_plugins script does not have the correct permission either. Here is the "ls -al" from jenkins@rosindustrial.org (note i fixed the issue with run_build_scripts.sh). This is from the "ros-industrial" branch.
-rwxr-xr-x 1 jenkins nogroup 285 Oct 14 10:57 build_catkin_workspace.sh -rwxr-xr-x 1 jenkins nogroup 1588 Aug 14 13:02 check_workspace_status.sh -rwxr-xr-x 1 jenkins nogroup 136185 Aug 14 13:02 cpplint.py -rwxr-xr-x 1 jenkins nogroup 775 Aug 14 13:02 create_catkin_workspace.sh -rwxr-xr-x 1 jenkins nogroup 960 Oct 14 10:57 create_jenkins_job.sh -rwxr-xr-x 1 jenkins nogroup 36060 Aug 14 13:02 gcovr -rw-r--r-- 1 jenkins nogroup 1135 Oct 14 10:57 install_plugins.sh -rw-r--r-- 1 jenkins nogroup 200 Oct 14 10:57 plugin_list.txt -rwxr-xr-x 1 jenkins nogroup 591 Oct 16 17:40 run_build_scripts.sh -rwxr-xr-x 1 jenkins nogroup 1045 Aug 14 13:02 run_codecount.bash -rwxr-xr-x 1 jenkins nogroup 669 Aug 14 13:02 run_cppcheck.bash -rwxr-xr-x 1 jenkins nogroup 1423 Oct 16 11:30 run_cpplint.bash -rwxr-xr-x 1 jenkins nogroup 1520 Oct 14 10:57 trigger_jobs.sh -rwxr-xr-x 1 jenkins nogroup 615 Aug 14 13:02 update_catkin_workspace.sh
Builds were failing on jenkins because the new run_build_scrips.sh does not have execution privileges. See: http://jenkins.rosindustrial.org/job/ros_industrial_groovy_dev/30/console
After adding the correct permissions (i.e. chmod +x), the build completed