Honeycomb packages depend on specific vpp package.

While such behavior is good for master branch, might not be as good for stable branches.

And is definitely not good for release artifacts.

For master branch api changes on vpp side occur more often making hc incompatible with most current vpp.

There is window between publishing vpp artifacts and publishing hc artifacts when incompatibility occur.

In case vpp job publishes artifacts and ends with failure, hc job needs to be started manually.

For stable branch such changes occur less often.

For release artifacts it is very unlikely to have such change.

Release artifacts are copied from stable branch,

so perhaps behaviour of hc integration jobs that publish debs/rpms,

should be altered to use range of supported versions instead of single specific vpp version.

Others possibilities needs to be investigated.