Skip to content
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

Supporting Ubuntu Wily in Continuous Integration / MoveIt! #222

Closed
davetcoleman opened this issue Sep 16, 2016 · 10 comments
Closed

Supporting Ubuntu Wily in Continuous Integration / MoveIt! #222

davetcoleman opened this issue Sep 16, 2016 · 10 comments

Comments

@davetcoleman
Copy link
Member

@rhaschke requested I add Wily (Ubuntu 15.10) testing to our Travis setup. It no longer appears as easy than when I first agreed to it - there are not ROS Docker images for it, for example (@ruffsl).

I also noticed that Wily is already end of life, so I was surprised that ROS Kinetic is still supporting it

All of this is important because we've been switching to new urdfdom headers here and here but they are missing in Wily.

Do we really need to support Wily in MoveIt? Do we have users who are going to, in the future when we finally release MoveIt! for Kinetic, choose to use an end of life non-LTS version of Ubuntu?

This might be an outrageous question and I suppose we'll run into issues with the ROS buildfarm, but just thought I'd throw the question out there. At bare minimum, I'm not sure its worth me building custom ROS Dockers and doing lots of modifications to our Travis scripts.

@v4hn
Copy link
Contributor

v4hn commented Sep 16, 2016

Wow, I didn't expect wily is eol already, but sure, time flies..
For how long does OSRF plan to build packages for wily?
I'd say that we do not need to support it anymore the moment they stop building packages.
No idea who would be best to ping about this at osrf.

Given the circumstances I believe this is yet another artificial problem arising due to all the release overhead: Nobody will switch to Wily anymore and MoveIt never worked on kinetic until recently.

@davetcoleman
Copy link
Member Author

davetcoleman commented Sep 16, 2016

This guy claims support should have already been dropped, but @tfoote is certainly the best person to ask

@tfoote
Copy link
Contributor

tfoote commented Sep 16, 2016

As linked Wily is a Kinetic target platform. It should generally be thought of as the low water mark for changes.

We are still building Kinetic debs for Wily. There's one or two changes we need to make to the buildfarm to support turning it off but we have not had time to make the upgrades.

@davetcoleman
Copy link
Member Author

So it will be turned off soon? Do you have a estimate for when? I think this is a nod that we will skip special rules to allow MoveIt! to be released for Wily

@tfoote
Copy link
Contributor

tfoote commented Sep 16, 2016

I doubt that it will happen soon, in the scale of a potential Kinetic moveit release.

@davetcoleman
Copy link
Member Author

@tfoote If we avoid adding the special #ifdef commands for wily, etc, can we still release MoveIt! into Kinetic using bloom or will it complain about the broken Wily target?

@tfoote
Copy link
Contributor

tfoote commented Sep 19, 2016

If it's compile type issues you will get daily emails when the buildfarm attempts to build Wily on each architecture.

@davetcoleman
Copy link
Member Author

I believe we decided we had to continue to support Wily because of ROS buildfarm requirements

@davetcoleman
Copy link
Member Author

We are still being blocked from releasing because of Wily, so I've reopened this discussion for all of ROS on Discourse

@davetcoleman
Copy link
Member Author

I've created a test for Wily moveit/moveit_ci#20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants