Closed flynneva closed 3 years ago
more than happy to make a PR with the changes once given the "green light"
I've had a lot of problems in the past with ros-tooling/setup-ros
. Specifically, they do a lot of tests and commands that aren't necessary in most cases and when something changes in a ROS package that they use, it breaks their jobs and the only way to fix it is to wait for them to find the bug, release a new version, then for the maintainer of the repos that use it to update their version. While the CI job that is used now may look custom, it's very standardized. The only part that would make it more portable to other repos is to replace the repo name in the script with $GITHUB_REPOSITORY
. This adds an extra directory but everything would still work fine.
that may have been true about setup-ros
a few months ago....it definitely isnt today. go ahead and look at what it runs. it is (almost exactly) the commands you are running in your setup.
I'm willing to give it a shot again. Go ahead with the PR.
closed with #34
the current CI strategy for this repo looks pretty custom (straight up bash commands in a list).
would we be able to switch over to the more standard
ros-tooling/setup-ros
andros-tooling/actions-ros-ci
.ive went ahead and made these changes on my fork of this repo if you'd like to check it out.