How should I build Debian packages on a local build server?
We're migrating from Fuerte to Hydro (rosbuild to catkin, more specifically), and all our existing build scripts that generate Fuerte-package-based Debian packages will no longer work. I understand the recommended approach to building Debian packages from catkin packages is to use bloom, but bloom seems very oriented to code that's released to others.
What is the recommended approach to automatically building and internally releasing Debian packages from local repositories? Ideally, every commit to our 'develop' branch would automatically generate a new Debian package for use on our test robots (likely without bumping package.xml version) and every commit to our 'master' branch would generate Debian packages for use on our production robots (with an associated bump to package.xml version). (To be clear, when I reference bumping version numbers, I mean commits to 'develop' don't constitute a new version of code for us, just another commit to be included in the next version number when they're all merged into 'master', ala git-flow.) And ideally, our Debian packages would include the git-hash in the Debian version, but I'm not clear on how to get a git-hash into the package.xml version number?
I've tried using bloom and it seems to create debs for the packages I've tested, but it's a very manual process (lots of questions to answer) and there's parts that suggest the new release will be advertised in official repos (via pull request) which is not OK.
Thanks for your help.