ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Prerelease tests with Bloom on first-release

asked 2015-01-28 10:50:56 -0600

dornhege gravatar image

updated 2015-01-28 10:51:17 -0600


I'm releasing a package with bloom for the first time and I'd like to run a prerelease test.

I'm following this tutorial: and everything works fine until I arrive at Step 4 here:

Now, obviously the pre-release site doesn't know my repository, yet, because there is not entry in the release.yaml file at all. However, if I do open the pull-request to get that in there, I'd release it without ever testing. Am I missing some step in between or what is the correct way to proceed?

As a side-note I've entered bloom-release multiple times and it's bumped the version each time. Is there any way to reset that, so I don't have unnecessary versions in between? I'm OK with resetting the release repo as that's new anyways.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2015-01-28 13:15:24 -0600

William gravatar image

updated 2015-01-28 13:15:52 -0600

The prerelease website can test your package based on data from three places:

  • The repository and branch listed in your source entry in the distribution.yaml on ros/rosdistro
    • This is the devel option.
  • The release repository and the "release" branch for each package.
    • Since this is a branch it will be updated after you push from bloom, but before you submit the pull request.
    • This is the latest option.
  • The latest released version of your package.
    • This is the x.y.z option, where x, y, and z are numbers for you package's most recent released version.

Now the question is, should you do a prerelease? The prerelease job does something that no other job does, it downloads, builds, and tests released packages which depend on your packages. This is really awesome if you are releasing a new version of a package which has already been released, but it is strictly less useful when you are releasing a package for the first time, since that means there are no released packages which can depend on you yet.

On the first release into a ROS distribution, I would recommend either just not doing a prerelease or doing the binary build test locally, see:

For Jade we plan to roll out a new tool which allows you to do pre-releases locally and with more control. This should make it easier to debug pre-releases and faster to run them since you don't have to wait on our farm which gets pretty backed up on pre-releases.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2015-01-28 10:50:56 -0600

Seen: 237 times

Last updated: Jan 28 '15