add rosinstall file for all ros-industrial repos

[ipa-nhg]

No description provided.

[gavanderhoorn]

This looks like a bit less than the 55 repositories we have in ros-industrial. Should we perhaps add what sort of selection process was used to arrive at this subset?

---

Edit: you opened the PR against indigo-devel (there is no other branch, I know), so perhaps we should also set the version field for all repositories listed to whatever is released into Indigo in this .rosinstall file.

[ipa-nhg]

Yes, I am agree.

My goal was use the rosinstall files to check with travis the current status of the most used ros-i official software (to some extend related to the idea of the documentation of a general overview of the software status ros-industrial/ros_industrial_issues#55 (comment)...). May we can create define some categories or types or repositories and create rosinstall for each category. For example the *_experimental repos.

[gavanderhoorn]

Most (all?) of the repositories that are in the .rosinstall file would seem to have regular Travis builds already, would showing the badges from the last Travis build not suffice?

Or are you specifically looking to catch regressions due to changes upstream?

[ipa-nhg]

I was thinking on play a bit with the branches. To be honest when I tried to solve this I got crazy trying to find the DISTRO convention/policy of each repo. A rosinstall file where you can define together the URL and the branch and that can be easily tested using travis for a concrete DISTRO can help a lot solving this type of generic issues and to document properly the software development status of the organization.
P.S. If you don't want to use this repo for testing I can also keep the travis configuration in a branch of my fork or just test the repo using industrial_ci locally, no problem it is also ok for me.

---

Update:
Trying to build using industrial_ci locally the listed repos I found a couple of them with a customized travis configuration that are not working with the generic one...