Skip to content

Commit

Permalink
[ci] Stop using ros-tooling/setup-ros (#363)
Browse files Browse the repository at this point in the history
It runs `sudo pip install --upgrade`, which in general we don't, especially for `numpy`
  • Loading branch information
EricCousineau-TRI authored Jul 26, 2024
1 parent eff1806 commit 5f6ead1
Showing 1 changed file with 3 additions and 12 deletions.
15 changes: 3 additions & 12 deletions .github/workflows/bazelized_drake_ros.yml
Original file line number Diff line number Diff line change
Expand Up @@ -39,10 +39,6 @@ jobs:
- name: Configure drake_ros Bazel for CI
run: ln -s ../.github/ci.bazelrc ./user.bazelrc
working-directory: drake_ros
- name: Install ROS tools (like rosdep)
uses: ros-tooling/setup-ros@v0.4
- name: Update rosdep data
run: rosdep update
- name: Install bazel_ros2_rules dependencies
# TODO(sloretz) make bazel_ros2_rules/setup/install_prereqs.sh
run: |
Expand All @@ -54,16 +50,11 @@ jobs:
- name: Install Drake's dependencies
run: yes | sudo ./bazel-drake_ros/external/drake/setup/ubuntu/install_prereqs.sh
working-directory: drake_ros
- name: Install ROS tarball's dependencies
# TODO(sloretz) can't use rosdep here because we need the archive downloaded,
# but can't download the archive with bazel until we have the dependencies installed
# so bazel_ros2_rules can inspect it.
run: |
sudo apt-get install -y libconsole-bridge-dev
sudo rm -rf /var/lib/apt/lists/*
# CI for drake_ros.
- name: Install drake_ros's dependencies
run: yes | sudo ./setup/install_prereqs.sh
run: |
yes | sudo ./setup/install_prereqs.sh
rosdep update # As user.
working-directory: drake_ros
- name: Build drake_ros
run: export ROS_DISTRO=humble; bazel build //...
Expand Down

0 comments on commit 5f6ead1

Please sign in to comment.