-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: SITL test run: select ROS version based on ROS_DISTRO #11338
Conversation
The Included here: https://github.com/PX4/containers/blob/f8a68d73f6e3e7db829e8a86fe9cc5976917ddbb/docker/px4-dev/Dockerfile_ros-kinetic#L9 Changing to WIP... |
Working on updating images to support this --> #11606 |
b55491a
to
9983cb9
Compare
rebased |
9983cb9
to
4f2a8e3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not set the distro based on the OS distro?
This is a good idea, but I see issues with it. It would be fairly trivial if we assume this will only be used with Ubuntu. We could run something like |
Check this example: https://github.com/PX4/px4_ros_com/blob/master/scripts/setup_system.bash |
That's exactly what I said we could do. I don't want to assume that everyone only uses Ubuntu. |
ROS officially supports Ubuntu and Debian. Both Ubuntu and Debian support the |
There's nothing wrong with your statement. It's just beyond the scope of what I was going for here. I was only trying to dynamically source the correct ROS setup for CI purposes as stated in the title and the original post. I still think the default matching what is officially used for testing is fine as it is only used for that purpose. If users want to run this on their own machine, they should have already sourced the correct setup script for their environment as defined in the installation instructions for ROS. If users run this inside the px4 docker container the environment variable will be set. I don't see any issues with this as is. |
Good enough for now. We can continue to generalize further. |
As we introduce SITL testing on Melodic this is important as we'll have Kinetic at the same time.