Ask Your Question
0

Release specific version of a package

asked 2015-06-16 06:57:42 -0500

atp gravatar image

updated 2015-06-19 08:50:53 -0500

gvdhoorn gravatar image

I have the feeling that the wrong version of my package gets released when running bloom-release: 1.1.0-6 instead of 1.3.1., where the second number is in both the changelog.rst and the package.xml files. So, is there a way to make bloom-release use version 1.3.1? (I was assuming that it always takes the most recent version.)


Edit:

I did what William suggested. Can it be that Jenkins is having connection trouble? I got 46 messages in my email saying this:

See <http://jenkins.ros.org/job/ros-indigo-handle-detector_sourcedeb/46/>

[...]

urllib2.URLError: <urlopen error <urlopen error [Errno 111] **Connection refused**> (https://raw.github.com/ros/rosdistro/master/index.yaml)>

Build step 'Execute shell' marked build as failure
Build step 'Groovy Postbuild' marked build as failure
Description set:
edit retag flag offensive close merge delete

Comments

I suspect this is caused by having skipped a step and / or incorrect content of some of the involved files. Could you provide links to the relevant (release) repositories?

gvdhoorn gravatar image gvdhoorn  ( 2015-06-16 07:49:34 -0500 )edit

I guess that these are the relevant repositories:

https://github.com/atenpas/handle_det...

https://github.com/atenpas/handle_det...

The changelogs, e.g., are different.

atp gravatar image atp  ( 2015-06-16 13:45:56 -0500 )edit

Ping @William?

gvdhoorn gravatar image gvdhoorn  ( 2015-06-17 07:06:36 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2015-06-17 13:34:16 -0500

William gravatar image

Based on https://github.com/atenpas/handle_det... , it looks like your default branch is master, which contains a package.xml for version 1.1.0 . Looking at your release settings: https://github.com/atenpas/handle_det... , you are using the "default" branch. You need to run bloom-release with the additional argument --edit. That will prompt you to update your configuration before trying to release. Then for the development branch setting you should put indigo since that is branch you'd like to release from on your upstream repository.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2015-06-16 06:57:42 -0500

Seen: 60 times

Last updated: Jun 19 '15