Re: integration/distribution version issues

Luis Gomez

Just 2 things:

- The common distribution (opendaylight/pom.xml) has never been governed by auto-release or automatic bump for that matter, please recheck your links if you do not believe. Also the common distribution follows a different version schema than auto-release which I found to better for an SM project, btw TPCE (the only SM project) also follows the same schema.

- The only build issues I see below are related to the common distribution (-full- job) and these are usually related to the fact that we are not bumping the version just after release because TPCE (the only SM project) does not do that either so it will break all the way if we do that. The other option is to disable the TPCE project as I do sometimes and Sangwook did in his last patch, that way it can be bumped.

I think in general for test/quality purposes we are solely looking at the karaf distribution and the common distribution is only used at the moment of the release to include the SM projects. That was all the idea behind the common distribution, but we can change that if people have concerns.


On Nov 17, 2021, at 1:18 AM, Robert Varga <nite@...> wrote:

On 17/11/2021 08:26, Luis Gomez wrote:
I thought this was clear, at least to ODL old folks, the int/dist project holds 2 distributions:
Three, actually.

- 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.
Yes, and therefore the release lifecycle of int/dist is unlike any other project I have come across.

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.
Right-o, but unfortunately you are explaining something completely off-topic, so let me try to reiterate.

1. Ever since the dawn of autorelease MSI projects have agreed to bump the minor version, i.e. 1.2.0 -> 1.3.0

2. On Feb 22 this year, Anil branched stable/silicon, correctly bumping opendaylight/pom.xml from 0.14.0-SNAPSHOT to 0.15.0-SNAPSHOT:

3. On Apr 3 this year, you changed the versioning scheme on stable/silicon to 14.0.0-SNAPSHOT:

4. On Apr 22 this year, Guillaume made a similar change on then-master:

5. On Sep 21 this year, Anil branched stable/phosphorus, but unlike all the previous times, opendaylight/pom.xml's version was NOT updated:

6. On Sep 24 this year, the first successful distribution-merge-full-sulfur job run:, happily doing:

Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
Uploading to opendaylight-snapshot:
Uploaded to opendaylight-snapshot: (266 MB at 28 MB/s)
Uploading to opendaylight-snapshot:
Uploaded to opendaylight-snapshot: (982 B at 18 kB/s)
7. On Sep 24 this year, run-of-the mill distribution-merge-full-phosphorus ran:, happily doing this:

Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
Uploading to opendaylight-snapshot:
Uploaded to opendaylight-snapshot: (266 MB at 28 MB/s)
Uploading to opendaylight-snapshot:
Uploaded to opendaylight-snapshot: (982 B at 20 kB/s)
8. This continued for quite some time, i.e. the contents of opendaylight-15.0.0-SNAPSHOT flip-flopped between Sulfur and Phosphorus

9. On Oct 24 distribution-merge-full-phosphorus started publishing opendaylight-15.1.0-SNAPSHOT:

10. On Oct 24 distribution-merge-full-sulfur started failing:

11. On Nov 13 the last published opendaylight-15.0.0-SNAPSHOT expired in Nexus

12. On Nov 14 distribution-merge-full-sulfur started failing: with

ERROR: Failed to parse POMs
hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.opendaylight.integration:opendaylight:15.0.0-SNAPSHOT: Could not find artifact org.opendaylight.integration:karaf:pom:0.15.0-SNAPSHOT in opendaylight-snapshot ( and 'parent.relativePath' points at no local POM @ line 14, column 13

The bottom line is:

- int/dist setup was busted for almost two months
- job failures have been indicating this clearly for a month
- now finally everything fell apart
- it was a downstream user who detected this mess

I equally hope this explains.


For more information check this doc: <>
On Nov 16, 2021, at 9:08 PM, Robert Varga <nite@... <mailto: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.