[Discourse.ros.org] [Packaging and Release Management/Kinetic] Jenkins spams after releasing a package in kinetic

[Discourse.ros.org] [Packaging and Release Management/Kinetic] Jenkins spams after releasing a package in kinetic

I keep receiving mails from jenkins about jessie deb building failure. It fails to clone a branch that doesn't exist in release branch. Can anyone help me to fix this issue? I tried to rerun bloom_release to see if bloom creates `debian/ros-kinetic-rosbridge-suite_0.8.1-0_jessie` branch, but it doesn't seem to generate the branch.

[Discourse.ros.org] [Packaging and Release Management/Kinetic] Jenkins spams after releasing a package in kinetic

Can you provide your bloom console output ? Is there any warning about rosdep keys not OK ?
One reason bloom doesnt generate the branches sometimes is because the rosdep keys for Jessie are not resolved so it cannot create the control file accordingly.

When push.default is set to 'matching', git will push local branches
to the remote branches that already exist with the same name.

Since Git 2.0, Git defaults to the more conservative 'simple'
behavior, which only pushes the current branch to the corresponding
remote branch that 'git pull' uses to update the current branch.

See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)

Tip: Check to ensure that the debian tags created have the same version as the upstream version you are releasing.
Everything went as expected, you should check that the new tags match your expectations, and then push to the release repo with:
git push --all && git push --tags # You might have to add --force to the second command if you are over-writing existing tags
<== Released 'rosbridge_suite' using release track 'kinetic' successfully
==> git remote -v
origin [hidden email]:RobotWebTools-release/rosbridge_suite-release.git (fetch)
origin [hidden email]:RobotWebTools-release/rosbridge_suite-release.git (push)
Releasing complete, push to release repository?
Continue [Y/n]?
```

[Discourse.ros.org] [Packaging and Release Management/Kinetic] Jenkins spams after releasing a package in kinetic

Support for debian has been added in bloom 0.5.21. It looks like you still have 0.5.20 that is more than 2 years old. Can you try to upgrade python-bloom and python-rosdistro and try running bloom again ?

There should be a in invocation of `git-bloom-generate` looking like this in your console output:
`git-bloom-generate -y rosdebian --prefix release/kinetic kinetic -i 0 --os-name debian --os-not-required`