-
Notifications
You must be signed in to change notification settings - Fork 0
Groovy :: Wet Release
Daniel Stonier edited this page Jan 27, 2015
·
1 revision
sudo apt-get install python-bloom python-rosdep python-rospkg
- Make sure you are working from a 'groovy-devel' branch (not master). This is easier and ros convention.
- Add a rosinstall for your repos to rosdistro's doc for wiki documentation indexing.
- Add package details to rosdistro's groovy/release.yaml without the line about the version - this helps the prerelease indexer. Once these pull requests have been accepted, you can pre-release.
- Prerelease : submit the stack(s) for a trial run
- Set version and create tag
> cd rocon_msgs
> catkin_package_version --bump patch
> git commit -a -m "0.1.1"
> git push
> git tag 0.1.1 -m "first catkin release."
> git push --tags
Now to start releasing, i.e. blooming.
- Create a new repo at https://github.com/yujinrobot-release named rocon_multimaster-release. Initialise it with a readme to save some work.
Then just follow the official instructions. Important points when you create a new track (git-bloom-config):
- Set the repository name exactly to your repo name (e.g. 'kobuki'), not 'upstream' - convenience thing only.
- Upstream URI is your source repository uri (e.g. https://github.com/yujinrobot/kobuki)
- Use auto and make sure the upstream development branch is correct (e.g. groovy-devel)
Test it with a release, and then push everything in the release repo as the instructions say.
> git push --all && git push --tags
- Add info to rosdistro's groovy.yaml, the build farm will then start automatically making releases for you.
I typically create some scripts which help the process in yujin_release/catkin. For your package(s):
- Create a new folder and copy across the Makefile from one of the other folders.
- Replace the name of your stacks in the Makefile.
- Get all the sources and make sure they've been configured appropriately.
> make clone
- You might want to isolate a stack (just use one name in the REPO variable in the Makefile) for the bloom step.
- Prerelease : submit the stack(s) for a trial run
- Set version and create tag
TODO Update this to use catkin_prepare_release
> cd rocon_msgs
> catkin_package_version --bump patch
> git commit -a -m "0.1.1"
> git push
> git tag 0.1.1 -m "first catkin release."
> git push --tags
- Bloom it
make bloom
- Update your repo version numbers and package lists in rosdistro groovy or rosdistro hydro.
- Bloom - wet instructions
- Bloom First Release Instructions
- Bloom Release Instructions
- Jenkins - wet builds
- DebBuild List - list of current build status'.
- Build System SIG
Specific Issues
-
ecl_xxx : needs a version bump in
ecl_build/cmake/ecl_package.cmake, also versions.dox.
Could not resolve rosdep key xxx
Probably you need to re-initialise your rosdep database for groovy.
> sudo rm /etc/ros/rosdep/sources.list.d/20-default.list
> sudo rosdep init
> rosdep update
If you need to delete tag or branch first,
> git tag -d 0.1.7
> git push origin :refs/tags/0.1.7
> git push origin --delete groovy-devel