Re: integration/distribution version issues

Luis Gomez

I thought this was clear, at least to ODL old folks, the int/dist project holds 2 distributions:

- Karaf distribution (karaf/pom.xml) only containing Managed projects is also a Managed project and integrated with autorelease (automatic release & bump).
- Common distribution (opendaylight/pom.xml) containing Managed and Self Managed projects. This is a Self Managed project and therefore it has to be manually released, bumped, etc, just like any other SM project.

AFAIR the sanity test you are pointing out is the only test that uses the common distribution, all of our CSIT uses Karaf distribution. I hope this explains.


On Nov 16, 2021, at 9:08 PM, Robert Varga <nite@...> wrote:

On 17/11/2021 00:37, Daniel de la Rosa wrote:
Let me add more Robert and team to make sure that they see this email

This boils down to interaction between autorelease and int/dist.

autorelease assumes branch cutting involves bumping minor version, which has been true for all MSI projects since forever.

int/dist started violating that assumption by changing versioning scheme here:

I have no skin in this particular game, sorry.


On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via <> < <>> wrote:
   It appears that the versions in
   integration/distribution/opendaylight have not been updated, and
   some Jenkins jobs are failing: e.g.
   I submitted two patches to fix up the version issues for Sulfur &
   Silicon - Phosphorus seems okay.
   Shouldn't this be done automatically when it's released? Looks like
   release version bump to remove SNAPSHOT is done automatically but
   SNAPSHOT version is not updated for opendaylight artifact.

Join { to automatically receive all group messages.