|
Re: Jenkins Robot test failures
Venkatrangan Govindarajan
Hi,
There are other jobs with the same features that are not reporting these GC Failures.
I am checking if there is any other parameter that is different than these jobs.
Regards, Rangan
Hi,
I will check today evening and let you know
On Thu, Dec 9, 2021, 16:00 Dominik Vrbovsky <dominik.vrbovsky@...> wrote:
-- Venkatrangan Govindarajan
( When there is no wind...Row )
|
|
|
Re: Jenkins Robot test failures
Venkatrangan Govindarajan
Hi,
I will check today evening and let you know
On Thu, Dec 9, 2021, 16:00 Dominik Vrbovsky <dominik.vrbovsky@...> wrote:
|
|
|
Jenkins Robot test failures
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus SR1
Daniel de la Rosa
toggle quoted messageShow quoted text
On Wed, Dec 1, 2021 at 9:01 PM Luis Gomez < ecelgp@...> wrote: OK, I just released the distribution with the old job name, we can fix the name for the next release:
BR/Luis
I have just realized there is a typo in the distribution stage job:
If anyone can review & merge, I can release the distribution tomorrow morning.
BR/Luis
Thank you Christophe and all. . @Luis Gomez , you can now proceed to release Phosphorus SR1 distribution.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
-- Daniel de la Rosa ODL Release Manager
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus SR1
OK, I just released the distribution with the old job name, we can fix the name for the next release:
BR/Luis
I have just realized there is a typo in the distribution stage job:
If anyone can review & merge, I can release the distribution tomorrow morning.
BR/Luis
Thank you Christophe and all. . @Luis Gomez , you can now proceed to release Phosphorus SR1 distribution.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus SR1
I have just realized there is a typo in the distribution stage job:
If anyone can review & merge, I can release the distribution tomorrow morning.
BR/Luis
Thank you Christophe and all. . @Luis Gomez , you can now proceed to release Phosphorus SR1 distribution.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
Hello
FYI I’ve proposed an open talk about the release process for the next DDF so that we can debate about it.
About TransportPCE, since Silicon I can’t see any advantage to stay SM too
and I am personally pro integrating the managed release.
Though, until recently, most committers in the projects used to be reluctant to the idea.
Maybe we have to be more explicit in the documentation about the advantage to be in managed release and MRI.
Hope this helps
BR
Guillaume
De : integration-dev@... [mailto:integration-dev@...]
De la part de Sangwook Ha via lists.opendaylight.org
Envoyé : mercredi 17 novembre 2021 22:58
À : Robert Varga
Cc : Daniel de la Rosa; Luis Gomez; Anil Belur; Venkatrangan Govindarajan; integration-dev@...
Objet : Re: [E] Re: [integration-dev] integration/distribution version issues
I wasn't really questioning why there are two release tracks. Just that it would be nice and could be possible to make the process a little simpler & more automated to reduce confusion and potential mismatch.
If it can be further simplified with a single release track, that would be even better.
On Wed, Nov 17, 2021 at 1:15 PM Robert Varga <nite@...> wrote:
On 17/11/2021 21:12, Daniel de la Rosa wrote:
> AFAIK, TPCE is going to be managed from Sulfur or even Phosphorus so
> makes sense to consolidate to a single repo.
Yes, Silicon SR3 has shown TCPE can easily manage being an MRI project.
Unimgr is irrelevant, as they still work on kernel from a few years back.
Regards,
Robert
>
> On Wed, Nov 17, 2021 at 12:03 PM Luis Gomez <ecelgp@...
> <mailto:ecelgp@...>> wrote:
>
> BTW below I meant "consolidate back to single distribution".
>
>> On Nov 17, 2021, at 12:01 PM, Luis Gomez via
>> lists.opendaylight.org <http://lists.opendaylight.org>
>> <ecelgp=gmail.com@...
>> <mailto:ecelgp=gmail.com@...>> wrote:
>>
>> I think the part that is confusing is to have 2 distros so
>> different (life-cycle, release, tagging, etc) in the same repo, I
>> remember we did this long time back because we wanted to avoid
>> having a new repo for just 1 file (opendaylight/pom.xml) but since
>> then it has been only problematic and complex (e.g. different jobs
>> and processes for different folders in the repo).
>>
>> Ideally we should separate these 2 in its own repo, jobs, etc. Or
>> better, consolidate back to single repo if we can get TPCE to be a
>> managed project. For your question, the only reason we need 2
>> distribution releases is because there is one Self Managed
>> projects that actively participates in the ODL distribution. Also
>> see more details on why we are releasing 2 distros here:
>> https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html
>> <https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html>,
>> however all this managed vs self-managed release was invented in a
>> time where we had many projects in ODL and for me this does not
>> make sense anymore.
>>
>> BR/Luis
>>
>>
>>> On Nov 17, 2021, at 10:12 AM, Ha, Sangwook
>>> <sangwook.ha@... <mailto:sangwook.ha@...>> wrote:
>>>
>>> Regarding the version mismatch for the common release, what I
>>> meant was for the karaf version in 'opendaylight/pom.xml' and the
>>> other versions - for example, release tag '14.3.0' would have the
>>> karaf version of '0.14.3' in 'opendaylight/pom.xml' but the rest
>>> has '0.14.4'. So both '14.3.0' and 'release/silicon-sr4', when
>>> released, will have '0.14.4' as the version for all the
>>> artifacts, at least when looking at the repository.
>>>
>>> Thanks,
>>> Sangwook
>>>
>>> On Wed, Nov 17, 2021 at 8:42 AM Sangwook Ha
>>> vialists.opendaylight.org
>>> <http://lists.opendaylight.org/><sangwook.ha=verizon.com@...
>>> <mailto:verizon.com@...>> wrote:
>>>
>>> Looking at the release & version bump cycle, some of the
>>> steps may be simplified, and hopefully automated:
>>>
>>> - For each release of managed projects, release & version
>>> bump, are done separately a few days apart - is there any
>>> reason why this cannot be done together?
>>> - For 'opendaylight/pom.xml' there are multiple manual steps:
>>> can steps 2 & 3 be merged & done automatically?
>>> 1) activate profiles for self-managed projects
>>> 2) release
>>> 3) update versions and deactivate profiles for self-managed
>>> projects (sometimes the version bump is done in two separate
>>> steps: the artifact/karaf & self-managed project)
>>>
>>> And there are two different types of release tags - one for
>>> managed projects (e.g. release/silicon-sr3) and common
>>> release (14.3.0). The former does not update
>>> 'opendaylight/pom.xml' but the latter updates all the POM
>>> files. And this is confusing because all the versions except
>>> for 'opendaylight/pom.xml' have been bumped up by the time
>>> the release is made, and they have a version ahead of what
>>> the label says (e.g. for the tag '14.3.0' all the versions
>>> except for 'opendaylight/pom.xml' is '14.4.0').
>>>
>>> Thanks,
>>> Sangwook
>>>
>>> On Wed, Nov 17, 2021 at 1:18 AM Robert Varga <nite@...
>>> <mailto: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:
>>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95287&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=ENR9PpXLDJnLf8oj0CFmCy6I2-DJyiBg-QuGxqrVqeo&e=>
>>>
>>> 3. On Apr 3 this year, you changed the versioning scheme on
>>> stable/silicon to 14.0.0-SNAPSHOT:
>>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>
>>>
>>> 4. On Apr 22 this year, Guillaume made a similar change
>>> on then-master:
>>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95789&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9iErSEyYMtT51b3WuuFlfaOCzjzrM0rfNiTieYnz4sk&e=>
>>>
>>> 5. On Sep 21 this year, Anil branched stable/phosphorus,
>>> but unlike all
>>> the previous times, opendaylight/pom.xml's version was
>>> NOT updated:
>>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_97551&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=b2gMEGM11TqHOcmajjzqxrtpl_plrd6-iGSXNMPMgtk&e=>
>>>
>>> 6. On Sep 24 this year, the first successful
>>> distribution-merge-full-sulfur job run:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_2_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=vvu3dJ4xfCQGN8r8Sq5yvGZJOsxwgTDh2-chFAZI-AQ&e=>,
>>> happily doing:
>>>
>>> > Deploying the main artifact
>>> opendaylight-15.0.0-SNAPSHOT.tar.gz
>>> > Uploading to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.032546-2D1083.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=zkpg2NXBTpEBrbdFrbWwP3DSinbjI6tl3b2y1d3fSbc&e=>
>>> > Uploaded to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.032546-2D1083.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=zkpg2NXBTpEBrbdFrbWwP3DSinbjI6tl3b2y1d3fSbc&e=>(266
>>> MB at 28 MB/s)
>>> > Uploading to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>
>>> > Uploaded to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>(982
>>> B at 18 kB/s)
>>>
>>> 7. On Sep 24 this year, run-of-the mill
>>> distribution-merge-full-phosphorus ran:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dphosphorus_1170_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=NRQHagQKXYI37eCuNNxZk_NGDMEO2mv70Og7ihHTm7E&e=>,
>>> happily doing this:
>>>
>>> > Deploying the main artifact
>>> opendaylight-15.0.0-SNAPSHOT.tar.gz
>>> > Uploading to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.050736-2D1084.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=Wu2pVV6q_Q3IpHwh5-gnGyI150g80OOnBeerBuCntjM&e=>
>>> > Uploaded to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.050736-2D1084.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=Wu2pVV6q_Q3IpHwh5-gnGyI150g80OOnBeerBuCntjM&e=>(266
>>> MB at 28 MB/s)
>>> > Uploading to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>
>>> > Uploaded to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>(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:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dphosphorus_1322_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=N89v3gILmCt8bbXoFF9LDCy_QcQ7oDmRZFQGX6GnrFw&e=>
>>>
>>> 10. On Oct 24 distribution-merge-full-sulfur started failing:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_149_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=xqIIfBinvc3mnGgda8yTxzisC1RCo-lYP0ThkLeApGY&e=>
>>>
>>> 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:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_275_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=D4U5p9ZIQvNK7h2uP8kMtexO_XSAyxBDQegrVacdz8E&e=>
>>> 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
>>> (https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=QagcQWeamwXzRViXc1ebAN1-m7C4rZ1Ez7-l1Mkxsx0&e=>)
>>> 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.
>>>
>>> Bye,
>>> Robert
>>>
>>> >
>>> > For more information check this doc:
>>> >https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendaylight.org_projects_integration-2Ddistribution_en_latest_add-2Dproject-2Ddistribution.html&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=KjH8fYD5lRh1ZHIQqZDBirxlSN71MnGEd2oWvSn_VMk&e=>
>>> >
>>> <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendaylight.org_projects_integration-2Ddistribution_en_latest_add-2Dproject-2Ddistribution.html&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=KjH8fYD5lRh1ZHIQqZDBirxlSN71MnGEd2oWvSn_VMk&e=>>
>>> >
>>> > BR/Luis
>>> >
>>> >> On Nov 16, 2021, at 9:08 PM, Robert Varga <nite@...
>>> <mailto:nite@...>
>>> >> <mailto: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:
>>> >>https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>
>>> >>
>>> <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>>
>>> >>
>>> >> I have no skin in this particular game, sorry.
>>> >>
>>> >> Regards,
>>> >> Robert
>>> >>
>>> >>
>>> >>> On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via
>>> >>>lists.opendaylight.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=><http://lists.opendaylight.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=>>
>>> >>> <http://lists.opendaylight.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=><http://lists.opendaylight.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=>>>
>>> >>> <sangwook.ha=verizon.com@...
>>> <mailto:verizon.com@...>
>>> >>> <mailto:sangwook.ha
>>> <mailto:sangwook.ha>=verizon.com@...
>>> <mailto:verizon.com@...>>
>>> >>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>
>>> >>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>>>> wrote:
>>> >>> It appears that the versions in
>>> >>> integration/distribution/opendaylight have not
>>> been updated, and
>>> >>> some Jenkins jobs are failing: e.g.
>>> >>> openflowplugin-csit-1node-sanity-only-sulfur
>>> >>>
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.opendaylight.org_releng_view_openflowplugin_job_openflowplugin-2Dcsit-2D1node-2Dsanity-2Donly-2Dsulfur_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9-yg1w_WEYSWQSNCb-79v2kXDAiXhnHfcWSrorKuH44&e=>
>>> >>>
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.opendaylight.org_releng_view_openflowplugin_job_openflowplugin-2Dcsit-2D1node-2Dsanity-2Donly-2Dsulfur_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9-yg1w_WEYSWQSNCb-79v2kXDAiXhnHfcWSrorKuH44&e=>>>
>>> >>> 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.
>>> >>> Thanks,
>>> >>> Sangwook
>>> >>>
>>> >
>>>
>>>
>>
>>
>>
>
> --
> Daniel de la Rosa
> ODL Release Manager
>
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus SR1
Daniel de la Rosa
Thank you Christophe and all. . @Luis Gomez , you can now proceed to release Phosphorus SR1 distribution.
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus SR1
Christophe Betoule
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
|
|
|
[opendaylight-dev][release] OpenDaylight - Phosphorus SR1
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
I wasn't really questioning why there are two release tracks. Just that it would be nice and could be possible to make the process a little simpler & more automated to reduce confusion and potential mismatch.
If it can be further simplified with a single release track, that would be even better.
Thanks, Sangwook
On Wed, Nov 17, 2021 at 1:15 PM Robert Varga < nite@...> wrote: On 17/11/2021 21:12, Daniel de la Rosa wrote:
> AFAIK, TPCE is going to be managed from Sulfur or even Phosphorus so
> makes sense to consolidate to a single repo.
Yes, Silicon SR3 has shown TCPE can easily manage being an MRI project.
Unimgr is irrelevant, as they still work on kernel from a few years back.
Regards,
Robert
>
> On Wed, Nov 17, 2021 at 12:03 PM Luis Gomez <ecelgp@...
> <mailto:ecelgp@...>> wrote:
>
> BTW below I meant "consolidate back to single distribution".
>
>> On Nov 17, 2021, at 12:01 PM, Luis Gomez via
>> lists.opendaylight.org <http://lists.opendaylight.org>
>> <ecelgp=gmail.com@...
>> <mailto:ecelgp=gmail.com@...>> wrote:
>>
>> I think the part that is confusing is to have 2 distros so
>> different (life-cycle, release, tagging, etc) in the same repo, I
>> remember we did this long time back because we wanted to avoid
>> having a new repo for just 1 file (opendaylight/pom.xml) but since
>> then it has been only problematic and complex (e.g. different jobs
>> and processes for different folders in the repo).
>>
>> Ideally we should separate these 2 in its own repo, jobs, etc. Or
>> better, consolidate back to single repo if we can get TPCE to be a
>> managed project. For your question, the only reason we need 2
>> distribution releases is because there is one Self Managed
>> projects that actively participates in the ODL distribution. Also
>> see more details on why we are releasing 2 distros here:
>> https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html
>> <https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html>,
>> however all this managed vs self-managed release was invented in a
>> time where we had many projects in ODL and for me this does not
>> make sense anymore.
>>
>> BR/Luis
>>
>>
>>> On Nov 17, 2021, at 10:12 AM, Ha, Sangwook
>>> <sangwook.ha@... <mailto:sangwook.ha@...>> wrote:
>>>
>>> Regarding the version mismatch for the common release, what I
>>> meant was for the karaf version in 'opendaylight/pom.xml' and the
>>> other versions - for example, release tag '14.3.0' would have the
>>> karaf version of '0.14.3' in 'opendaylight/pom.xml' but the rest
>>> has '0.14.4'. So both '14.3.0' and 'release/silicon-sr4', when
>>> released, will have '0.14.4' as the version for all the
>>> artifacts, at least when looking at the repository.
>>>
>>> Thanks,
>>> Sangwook
>>>
>>> On Wed, Nov 17, 2021 at 8:42 AM Sangwook Ha
>>> vialists.opendaylight.org
>>> <http://lists.opendaylight.org/><sangwook.ha=verizon.com@...
>>> <mailto:verizon.com@...>> wrote:
>>>
>>> Looking at the release & version bump cycle, some of the
>>> steps may be simplified, and hopefully automated:
>>>
>>> - For each release of managed projects, release & version
>>> bump, are done separately a few days apart - is there any
>>> reason why this cannot be done together?
>>> - For 'opendaylight/pom.xml' there are multiple manual steps:
>>> can steps 2 & 3 be merged & done automatically?
>>> 1) activate profiles for self-managed projects
>>> 2) release
>>> 3) update versions and deactivate profiles for self-managed
>>> projects (sometimes the version bump is done in two separate
>>> steps: the artifact/karaf & self-managed project)
>>>
>>> And there are two different types of release tags - one for
>>> managed projects (e.g. release/silicon-sr3) and common
>>> release (14.3.0). The former does not update
>>> 'opendaylight/pom.xml' but the latter updates all the POM
>>> files. And this is confusing because all the versions except
>>> for 'opendaylight/pom.xml' have been bumped up by the time
>>> the release is made, and they have a version ahead of what
>>> the label says (e.g. for the tag '14.3.0' all the versions
>>> except for 'opendaylight/pom.xml' is '14.4.0').
>>>
>>> Thanks,
>>> Sangwook
>>>
>>> On Wed, Nov 17, 2021 at 1:18 AM Robert Varga <nite@...
>>> <mailto: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:
>>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95287&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=ENR9PpXLDJnLf8oj0CFmCy6I2-DJyiBg-QuGxqrVqeo&e=>
>>>
>>> 3. On Apr 3 this year, you changed the versioning scheme on
>>> stable/silicon to 14.0.0-SNAPSHOT:
>>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>
>>>
>>> 4. On Apr 22 this year, Guillaume made a similar change
>>> on then-master:
>>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95789&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9iErSEyYMtT51b3WuuFlfaOCzjzrM0rfNiTieYnz4sk&e=>
>>>
>>> 5. On Sep 21 this year, Anil branched stable/phosphorus,
>>> but unlike all
>>> the previous times, opendaylight/pom.xml's version was
>>> NOT updated:
>>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_97551&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=b2gMEGM11TqHOcmajjzqxrtpl_plrd6-iGSXNMPMgtk&e=>
>>>
>>> 6. On Sep 24 this year, the first successful
>>> distribution-merge-full-sulfur job run:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_2_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=vvu3dJ4xfCQGN8r8Sq5yvGZJOsxwgTDh2-chFAZI-AQ&e=>,
>>> happily doing:
>>>
>>> > Deploying the main artifact
>>> opendaylight-15.0.0-SNAPSHOT.tar.gz
>>> > Uploading to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.032546-2D1083.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=zkpg2NXBTpEBrbdFrbWwP3DSinbjI6tl3b2y1d3fSbc&e=>
>>> > Uploaded to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.032546-2D1083.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=zkpg2NXBTpEBrbdFrbWwP3DSinbjI6tl3b2y1d3fSbc&e=>(266
>>> MB at 28 MB/s)
>>> > Uploading to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>
>>> > Uploaded to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>(982
>>> B at 18 kB/s)
>>>
>>> 7. On Sep 24 this year, run-of-the mill
>>> distribution-merge-full-phosphorus ran:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dphosphorus_1170_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=NRQHagQKXYI37eCuNNxZk_NGDMEO2mv70Og7ihHTm7E&e=>,
>>> happily doing this:
>>>
>>> > Deploying the main artifact
>>> opendaylight-15.0.0-SNAPSHOT.tar.gz
>>> > Uploading to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.050736-2D1084.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=Wu2pVV6q_Q3IpHwh5-gnGyI150g80OOnBeerBuCntjM&e=>
>>> > Uploaded to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.050736-2D1084.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=Wu2pVV6q_Q3IpHwh5-gnGyI150g80OOnBeerBuCntjM&e=>(266
>>> MB at 28 MB/s)
>>> > Uploading to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>
>>> > Uploaded to
>>> opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>(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:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dphosphorus_1322_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=N89v3gILmCt8bbXoFF9LDCy_QcQ7oDmRZFQGX6GnrFw&e=>
>>>
>>> 10. On Oct 24 distribution-merge-full-sulfur started failing:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_149_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=xqIIfBinvc3mnGgda8yTxzisC1RCo-lYP0ThkLeApGY&e=>
>>>
>>> 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:
>>> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_275_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=D4U5p9ZIQvNK7h2uP8kMtexO_XSAyxBDQegrVacdz8E&e=>
>>> 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
>>> (https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=QagcQWeamwXzRViXc1ebAN1-m7C4rZ1Ez7-l1Mkxsx0&e=>)
>>> 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.
>>>
>>> Bye,
>>> Robert
>>>
>>> >
>>> > For more information check this doc:
>>> >https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendaylight.org_projects_integration-2Ddistribution_en_latest_add-2Dproject-2Ddistribution.html&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=KjH8fYD5lRh1ZHIQqZDBirxlSN71MnGEd2oWvSn_VMk&e=>
>>> >
>>> <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendaylight.org_projects_integration-2Ddistribution_en_latest_add-2Dproject-2Ddistribution.html&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=KjH8fYD5lRh1ZHIQqZDBirxlSN71MnGEd2oWvSn_VMk&e=>>
>>> >
>>> > BR/Luis
>>> >
>>> >> On Nov 16, 2021, at 9:08 PM, Robert Varga <nite@...
>>> <mailto:nite@...>
>>> >> <mailto: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:
>>> >>https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>
>>> >>
>>> <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>>
>>> >>
>>> >> I have no skin in this particular game, sorry.
>>> >>
>>> >> Regards,
>>> >> Robert
>>> >>
>>> >>
>>> >>> On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via
>>> >>>lists.opendaylight.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=><http://lists.opendaylight.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=>>
>>> >>> <http://lists.opendaylight.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=><http://lists.opendaylight.org
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=>>>
>>> >>> <sangwook.ha=verizon.com@...
>>> <mailto:verizon.com@...>
>>> >>> <mailto:sangwook.ha
>>> <mailto:sangwook.ha>=verizon.com@...
>>> <mailto:verizon.com@...>>
>>> >>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>
>>> >>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>>>> wrote:
>>> >>> It appears that the versions in
>>> >>> integration/distribution/opendaylight have not
>>> been updated, and
>>> >>> some Jenkins jobs are failing: e.g.
>>> >>> openflowplugin-csit-1node-sanity-only-sulfur
>>> >>>
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.opendaylight.org_releng_view_openflowplugin_job_openflowplugin-2Dcsit-2D1node-2Dsanity-2Donly-2Dsulfur_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9-yg1w_WEYSWQSNCb-79v2kXDAiXhnHfcWSrorKuH44&e=>
>>> >>>
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.opendaylight.org_releng_view_openflowplugin_job_openflowplugin-2Dcsit-2D1node-2Dsanity-2Donly-2Dsulfur_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9-yg1w_WEYSWQSNCb-79v2kXDAiXhnHfcWSrorKuH44&e=>>>
>>> >>> 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.
>>> >>> Thanks,
>>> >>> Sangwook
>>> >>>
>>> >
>>>
>>>
>>
>>
>>
>
> --
> Daniel de la Rosa
> ODL Release Manager
>
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
On 17/11/2021 21:12, Daniel de la Rosa wrote: AFAIK, TPCE is going to be managed from Sulfur or even Phosphorus so makes sense to consolidate to a single repo. Yes, Silicon SR3 has shown TCPE can easily manage being an MRI project. Unimgr is irrelevant, as they still work on kernel from a few years back. Regards, Robert On Wed, Nov 17, 2021 at 12:03 PM Luis Gomez <ecelgp@gmail.com <mailto:ecelgp@gmail.com>> wrote:
BTW below I meant "consolidate back to single distribution".
On Nov 17, 2021, at 12:01 PM, Luis Gomez via
lists.opendaylight.org <http://lists.opendaylight.org>
<ecelgp=gmail.com@lists.opendaylight.org
<mailto:ecelgp=gmail.com@lists.opendaylight.org>> wrote:
I think the part that is confusing is to have 2 distros so
different (life-cycle, release, tagging, etc) in the same repo, I
remember we did this long time back because we wanted to avoid
having a new repo for just 1 file (opendaylight/pom.xml) but since
then it has been only problematic and complex (e.g. different jobs
and processes for different folders in the repo).
Ideally we should separate these 2 in its own repo, jobs, etc. Or
better, consolidate back to single repo if we can get TPCE to be a
managed project. For your question, the only reason we need 2
distribution releases is because there is one Self Managed
projects that actively participates in the ODL distribution. Also
see more details on why we are releasing 2 distros here:
https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html
<https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html>,
however all this managed vs self-managed release was invented in a
time where we had many projects in ODL and for me this does not
make sense anymore.
BR/Luis
On Nov 17, 2021, at 10:12 AM, Ha, Sangwook
<sangwook.ha@verizon.com <mailto:sangwook.ha@verizon.com>> wrote:
Regarding the version mismatch for the common release, what I
meant was for the karaf version in 'opendaylight/pom.xml' and the
other versions - for example, release tag '14.3.0' would have the
karaf version of '0.14.3' in 'opendaylight/pom.xml' but the rest
has '0.14.4'. So both '14.3.0' and 'release/silicon-sr4', when
released, will have '0.14.4' as the version for all the
artifacts, at least when looking at the repository.
Thanks,
Sangwook
On Wed, Nov 17, 2021 at 8:42 AM Sangwook Ha
vialists.opendaylight.org
<http://lists.opendaylight.org/><sangwook.ha=verizon.com@lists.opendaylight.org
<mailto:verizon.com@lists.opendaylight.org>> wrote:
Looking at the release & version bump cycle, some of the
steps may be simplified, and hopefully automated:
- For each release of managed projects, release & version
bump, are done separately a few days apart - is there any
reason why this cannot be done together?
- For 'opendaylight/pom.xml' there are multiple manual steps:
can steps 2 & 3 be merged & done automatically?
1) activate profiles for self-managed projects
2) release
3) update versions and deactivate profiles for self-managed
projects (sometimes the version bump is done in two separate
steps: the artifact/karaf & self-managed project)
And there are two different types of release tags - one for
managed projects (e.g. release/silicon-sr3) and common
release (14.3.0). The former does not update
'opendaylight/pom.xml' but the latter updates all the POM
files. And this is confusing because all the versions except
for 'opendaylight/pom.xml' have been bumped up by the time
the release is made, and they have a version ahead of what
the label says (e.g. for the tag '14.3.0' all the versions
except for 'opendaylight/pom.xml' is '14.4.0').
Thanks,
Sangwook
On Wed, Nov 17, 2021 at 1:18 AM Robert Varga <nite@hq.sk
<mailto:nite@hq.sk>> 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:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95287&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=ENR9PpXLDJnLf8oj0CFmCy6I2-DJyiBg-QuGxqrVqeo&e=>
3. On Apr 3 this year, you changed the versioning scheme on
stable/silicon to 14.0.0-SNAPSHOT:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>
4. On Apr 22 this year, Guillaume made a similar change
on then-master:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95789&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9iErSEyYMtT51b3WuuFlfaOCzjzrM0rfNiTieYnz4sk&e=>
5. On Sep 21 this year, Anil branched stable/phosphorus,
but unlike all
the previous times, opendaylight/pom.xml's version was
NOT updated:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_97551&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=b2gMEGM11TqHOcmajjzqxrtpl_plrd6-iGSXNMPMgtk&e=>
6. On Sep 24 this year, the first successful
distribution-merge-full-sulfur job run:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_2_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=vvu3dJ4xfCQGN8r8Sq5yvGZJOsxwgTDh2-chFAZI-AQ&e=>,
happily doing:
> Deploying the main artifact
opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to
opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.032546-2D1083.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=zkpg2NXBTpEBrbdFrbWwP3DSinbjI6tl3b2y1d3fSbc&e=>
> Uploaded to
opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.032546-2D1083.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=zkpg2NXBTpEBrbdFrbWwP3DSinbjI6tl3b2y1d3fSbc&e=>(266
MB at 28 MB/s)
> Uploading to
opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>
> Uploaded to
opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>(982
B at 18 kB/s)
7. On Sep 24 this year, run-of-the mill
distribution-merge-full-phosphorus ran:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dphosphorus_1170_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=NRQHagQKXYI37eCuNNxZk_NGDMEO2mv70Og7ihHTm7E&e=>,
happily doing this:
> Deploying the main artifact
opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to
opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.050736-2D1084.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=Wu2pVV6q_Q3IpHwh5-gnGyI150g80OOnBeerBuCntjM&e=>
> Uploaded to
opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_opendaylight-2D15.0.0-2D20210924.050736-2D1084.tar.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=Wu2pVV6q_Q3IpHwh5-gnGyI150g80OOnBeerBuCntjM&e=>(266
MB at 28 MB/s)
> Uploading to
opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>
> Uploaded to
opendaylight-snapshot:https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_org_opendaylight_integration_opendaylight_15.0.0-2DSNAPSHOT_maven-2Dmetadata.xml&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=SJolPkRRdilIVEdj7-Y7-OWN1Cq5-gP6jxLHbVelBuE&e=>(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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dphosphorus_1322_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=N89v3gILmCt8bbXoFF9LDCy_QcQ7oDmRZFQGX6GnrFw&e=>
10. On Oct 24 distribution-merge-full-sulfur started failing:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_149_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=xqIIfBinvc3mnGgda8yTxzisC1RCo-lYP0ThkLeApGY&e=>
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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz
<https://urldefense.proofpoint.com/v2/url?u=https-3A__s3-2Dlogs.opendaylight.org_logs_releng_vex-2Dyul-2Dodl-2Djenkins-2D1_distribution-2Dmerge-2Dfull-2Dsulfur_275_console.log.gz&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=D4U5p9ZIQvNK7h2uP8kMtexO_XSAyxBDQegrVacdz8E&e=>
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
(https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/
<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.opendaylight.org_content_repositories_opendaylight.snapshot_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=QagcQWeamwXzRViXc1ebAN1-m7C4rZ1Ez7-l1Mkxsx0&e=>)
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.
Bye,
Robert
>
> For more information check this doc:
>https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendaylight.org_projects_integration-2Ddistribution_en_latest_add-2Dproject-2Ddistribution.html&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=KjH8fYD5lRh1ZHIQqZDBirxlSN71MnGEd2oWvSn_VMk&e=>
>
<https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendaylight.org_projects_integration-2Ddistribution_en_latest_add-2Dproject-2Ddistribution.html&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=KjH8fYD5lRh1ZHIQqZDBirxlSN71MnGEd2oWvSn_VMk&e=>>
>
> BR/Luis
>
>> On Nov 16, 2021, at 9:08 PM, Robert Varga <nite@hq.sk
<mailto:nite@hq.sk>
>> <mailto:nite@hq.sk <mailto:nite@hq.sk>>> 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:
>>https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>
>>
<https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.opendaylight.org_gerrit_c_integration_distribution_-2B_95655&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=MGT0sdWpHRSK7_GmrqHtdvizWNb81gKttPVpJK0aGmE&e=>>
>>
>> I have no skin in this particular game, sorry.
>>
>> Regards,
>> Robert
>>
>>
>>> On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via
>>>lists.opendaylight.org
<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=><http://lists.opendaylight.org
<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=>>
>>> <http://lists.opendaylight.org
<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=><http://lists.opendaylight.org
<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.opendaylight.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=5NvKBEoxUPP9AWNWyPkLtYgZKvZw_VKmWGkMvwuRDKo&e=>>>
>>> <sangwook.ha=verizon.com@lists.opendaylight.org
<mailto:verizon.com@lists.opendaylight.org>
>>> <mailto:sangwook.ha
<mailto:sangwook.ha>=verizon.com@lists.opendaylight.org
<mailto:verizon.com@lists.opendaylight.org>>
>>> <mailto:verizon.com@lists.opendaylight.org
<mailto:verizon.com@lists.opendaylight.org>
>>> <mailto:verizon.com@lists.opendaylight.org
<mailto:verizon.com@lists.opendaylight.org>>>> wrote:
>>> It appears that the versions in
>>> integration/distribution/opendaylight have not
been updated, and
>>> some Jenkins jobs are failing: e.g.
>>> openflowplugin-csit-1node-sanity-only-sulfur
>>>
<https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
<https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.opendaylight.org_releng_view_openflowplugin_job_openflowplugin-2Dcsit-2D1node-2Dsanity-2Donly-2Dsulfur_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9-yg1w_WEYSWQSNCb-79v2kXDAiXhnHfcWSrorKuH44&e=>
>>>
<https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
<https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.opendaylight.org_releng_view_openflowplugin_job_openflowplugin-2Dcsit-2D1node-2Dsanity-2Donly-2Dsulfur_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=tFlYQtdB5h1Aic2Ti7Ncev9qFTcOZoMgJ6CVN_sDUdU&m=G6GgOuRz8JUyBVgXJXABmtWNg681fxZm7hUpvWAXoJI&s=9-yg1w_WEYSWQSNCb-79v2kXDAiXhnHfcWSrorKuH44&e=>>>
>>> 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.
>>> Thanks,
>>> Sangwook
>>>
>
--
Daniel de la Rosa
ODL Release Manager
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
On 17/11/2021 17:42, Ha, Sangwook wrote: Looking at the release & version bump cycle, some of the steps may be simplified, and hopefully automated:
- For each release of managed projects, release & version bump, are done separately a few days apart - is there any reason why this cannot be done together? Yes there is and there is quite a bit of history attached to that. Our governance clearly states that each project is independent, which in this context means is free to release whenever as well as can decide to release outside of Simultaneous Release. During our initial (Hydrogen, 2014) release, we have had all projects integrating on SNAPSHOTs and the release party was ... not awesome. If you see git tags like "jenkins-controller-bulk-release-prepare-only-2-1", those are from that period. There were multiple technical reasons why it did not go so well. As a reaction to that, autorelease was created, to have all projects still integrated on SNAPSHOTs, but projects gave up their right to release on their own and instead all projects were release by LFN personnel in one large chunk -- we are still doing this for MSI projects. The experience of being integrated on SNAPSHOTs was ... not exactly great -- it lead to the creation of validate-autorelease and distribution-check jobs, which gate every patch so that it does not happen to break downstreams. We have mostly addressed the technical issues by 2017 and started peeling projects away from autorelease with odlparent-2.0.0 (IIRC). Fast forward to today and autorelease does not carry a single kernel project. With that context, I will never agree to going for "release together" -- that amounts to autorelease hell. I have endured it for years upon years and have toiled sweat and blood to get out of it. I am *NEVER* going back to that, period. Can we do better than we are doing today? Certainly. There are multiple reasons why kernel project releases happen "a few days apart". It is mostly a manual process and you can probably guess whose time is being spent on it. There is silver lining, though, as Nexus promotions take ~30 minutes for most projects, not 2+ hours like they used to just two months ago. Now if we only had reliable automation taking advantage of that... Regards, Robert
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
Daniel de la Rosa
AFAIK, TPCE is going to be managed from Sulfur or even Phosphorus so makes sense to consolidate to a single repo.
On Wed, Nov 17, 2021 at 12:03 PM Luis Gomez < ecelgp@...> wrote: BTW below I meant "consolidate back to single distribution".
I think the part that is confusing is to have 2 distros so different (life-cycle, release, tagging, etc) in the same repo, I remember we did this long time back because we wanted to avoid having a new repo for just 1 file (opendaylight/pom.xml) but since then it has been only problematic and complex (e.g. different jobs and processes for different folders in the repo).
Ideally we should separate these 2 in its own repo, jobs, etc. Or better, consolidate back to single repo if we can get TPCE to be a managed project. For your question, the only reason we need 2 distribution releases is because there is one Self Managed projects that actively participates in the ODL distribution. Also see more details on why we are releasing 2 distros here: https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html, however all this managed vs self-managed release was invented in a time where we had many projects in ODL and for me this does not make sense anymore.
BR/Luis
Regarding the version mismatch for the common release, what I meant was for the karaf version in 'opendaylight/pom.xml' and the other versions - for example, release tag '14.3.0' would have the karaf version of '0.14.3' in 'opendaylight/pom.xml' but the rest has '0.14.4'. So both '14.3.0' and 'release/silicon-sr4', when released, will have '0.14.4' as the version for all the artifacts, at least when looking at the repository.
Thanks, Sangwook Looking at the release & version bump cycle, some of the steps may be simplified, and hopefully automated:
- For each release of managed projects, release & version bump, are done separately a few days apart - is there any reason why this cannot be done together? - For 'opendaylight/pom.xml' there are multiple manual steps: can steps 2 & 3 be merged & done automatically?
1) activate profiles for self-managed projects 2) release 3) update versions and deactivate profiles for self-managed projects (sometimes the version bump is done in two separate steps: the artifact/karaf & self-managed project)
And there are two different types of release tags - one for managed projects (e.g. release/silicon-sr3) and common release (14.3.0). The former does not update 'opendaylight/pom.xml' but the latter updates all the POM files. And this is confusing because all the versions except for 'opendaylight/pom.xml' have been bumped up by the time the release is made, and they have a version ahead of what the label says (e.g. for the tag '14.3.0' all the versions except for 'opendaylight/pom.xml' is '14.4.0').
Thanks, Sangwook On Wed, 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:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
3. On Apr 3 this year, you changed the versioning scheme on
stable/silicon to 14.0.0-SNAPSHOT:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
4. On Apr 22 this year, Guillaume made a similar change on then-master:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
5. On Sep 21 this year, Anil branched stable/phosphorus, but unlike all
the previous times, opendaylight/pom.xml's version was NOT updated:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
6. On Sep 24 this year, the first successful
distribution-merge-full-sulfur job run:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz,
happily doing:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (982 B at 18 kB/s)
7. On Sep 24 this year, run-of-the mill
distribution-merge-full-phosphorus ran:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz,
happily doing this:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
10. On Oct 24 distribution-merge-full-sulfur started failing:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz
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 (https://nexus.opendaylight.org/content/repositories/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.
Bye,
Robert
>
> For more information check this doc:
> https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
> <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html>
>
> BR/Luis
>
>> 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:
>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>> <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655>
>>
>> I have no skin in this particular game, sorry.
>>
>> Regards,
>> Robert
>>
>>
>>> On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via
>>> lists.opendaylight.org <http://lists.opendaylight.org>
>>> <http://lists.opendaylight.org <http://lists.opendaylight.org>>
>>> <sangwook.ha=verizon.com@...
>>> <mailto:sangwook.ha=verizon.com@...>
>>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>>> wrote:
>>> It appears that the versions in
>>> integration/distribution/opendaylight have not been updated, and
>>> some Jenkins jobs are failing: e.g.
>>> openflowplugin-csit-1node-sanity-only-sulfur
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/>>
>>> 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.
>>> Thanks,
>>> Sangwook
>>>
>
-- Daniel de la Rosa ODL Release Manager
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
BTW below I meant "consolidate back to single distribution".
I think the part that is confusing is to have 2 distros so different (life-cycle, release, tagging, etc) in the same repo, I remember we did this long time back because we wanted to avoid having a new repo for just 1 file (opendaylight/pom.xml) but since then it has been only problematic and complex (e.g. different jobs and processes for different folders in the repo).
Ideally we should separate these 2 in its own repo, jobs, etc. Or better, consolidate back to single repo if we can get TPCE to be a managed project. For your question, the only reason we need 2 distribution releases is because there is one Self Managed projects that actively participates in the ODL distribution. Also see more details on why we are releasing 2 distros here: https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html, however all this managed vs self-managed release was invented in a time where we had many projects in ODL and for me this does not make sense anymore.
BR/Luis
Regarding the version mismatch for the common release, what I meant was for the karaf version in 'opendaylight/pom.xml' and the other versions - for example, release tag '14.3.0' would have the karaf version of '0.14.3' in 'opendaylight/pom.xml' but the rest has '0.14.4'. So both '14.3.0' and 'release/silicon-sr4', when released, will have '0.14.4' as the version for all the artifacts, at least when looking at the repository.
Thanks, Sangwook Looking at the release & version bump cycle, some of the steps may be simplified, and hopefully automated:
- For each release of managed projects, release & version bump, are done separately a few days apart - is there any reason why this cannot be done together? - For 'opendaylight/pom.xml' there are multiple manual steps: can steps 2 & 3 be merged & done automatically?
1) activate profiles for self-managed projects 2) release 3) update versions and deactivate profiles for self-managed projects (sometimes the version bump is done in two separate steps: the artifact/karaf & self-managed project)
And there are two different types of release tags - one for managed projects (e.g. release/silicon-sr3) and common release (14.3.0). The former does not update 'opendaylight/pom.xml' but the latter updates all the POM files. And this is confusing because all the versions except for 'opendaylight/pom.xml' have been bumped up by the time the release is made, and they have a version ahead of what the label says (e.g. for the tag '14.3.0' all the versions except for 'opendaylight/pom.xml' is '14.4.0').
Thanks, Sangwook On Wed, 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:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
3. On Apr 3 this year, you changed the versioning scheme on
stable/silicon to 14.0.0-SNAPSHOT:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
4. On Apr 22 this year, Guillaume made a similar change on then-master:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
5. On Sep 21 this year, Anil branched stable/phosphorus, but unlike all
the previous times, opendaylight/pom.xml's version was NOT updated:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
6. On Sep 24 this year, the first successful
distribution-merge-full-sulfur job run:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz,
happily doing:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (982 B at 18 kB/s)
7. On Sep 24 this year, run-of-the mill
distribution-merge-full-phosphorus ran:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz,
happily doing this:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
10. On Oct 24 distribution-merge-full-sulfur started failing:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz
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 (https://nexus.opendaylight.org/content/repositories/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.
Bye,
Robert
>
> For more information check this doc:
> https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
> <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html>
>
> BR/Luis
>
>> 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:
>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>> <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655>
>>
>> I have no skin in this particular game, sorry.
>>
>> Regards,
>> Robert
>>
>>
>>> On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via
>>> lists.opendaylight.org <http://lists.opendaylight.org>
>>> <http://lists.opendaylight.org <http://lists.opendaylight.org>>
>>> <sangwook.ha=verizon.com@...
>>> <mailto:sangwook.ha=verizon.com@...>
>>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>>> wrote:
>>> It appears that the versions in
>>> integration/distribution/opendaylight have not been updated, and
>>> some Jenkins jobs are failing: e.g.
>>> openflowplugin-csit-1node-sanity-only-sulfur
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/>>
>>> 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.
>>> Thanks,
>>> Sangwook
>>>
>
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
I think the part that is confusing is to have 2 distros so different (life-cycle, release, tagging, etc) in the same repo, I remember we did this long time back because we wanted to avoid having a new repo for just 1 file (opendaylight/pom.xml) but since then it has been only problematic and complex (e.g. different jobs and processes for different folders in the repo).
Ideally we should separate these 2 in its own repo, jobs, etc. Or better, consolidate back to single repo if we can get TPCE to be a managed project. For your question, the only reason we need 2 distribution releases is because there is one Self Managed projects that actively participates in the ODL distribution. Also see more details on why we are releasing 2 distros here: https://docs.opendaylight.org/en/stable-phosphorus/release-process/managed-release.html, however all this managed vs self-managed release was invented in a time where we had many projects in ODL and for me this does not make sense anymore.
BR/Luis
Regarding the version mismatch for the common release, what I meant was for the karaf version in 'opendaylight/pom.xml' and the other versions - for example, release tag '14.3.0' would have the karaf version of '0.14.3' in 'opendaylight/pom.xml' but the rest has '0.14.4'. So both '14.3.0' and 'release/silicon-sr4', when released, will have '0.14.4' as the version for all the artifacts, at least when looking at the repository.
Thanks, Sangwook Looking at the release & version bump cycle, some of the steps may be simplified, and hopefully automated:
- For each release of managed projects, release & version bump, are done separately a few days apart - is there any reason why this cannot be done together? - For 'opendaylight/pom.xml' there are multiple manual steps: can steps 2 & 3 be merged & done automatically?
1) activate profiles for self-managed projects 2) release 3) update versions and deactivate profiles for self-managed projects (sometimes the version bump is done in two separate steps: the artifact/karaf & self-managed project)
And there are two different types of release tags - one for managed projects (e.g. release/silicon-sr3) and common release (14.3.0). The former does not update 'opendaylight/pom.xml' but the latter updates all the POM files. And this is confusing because all the versions except for 'opendaylight/pom.xml' have been bumped up by the time the release is made, and they have a version ahead of what the label says (e.g. for the tag '14.3.0' all the versions except for 'opendaylight/pom.xml' is '14.4.0').
Thanks, Sangwook On Wed, 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:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
3. On Apr 3 this year, you changed the versioning scheme on
stable/silicon to 14.0.0-SNAPSHOT:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
4. On Apr 22 this year, Guillaume made a similar change on then-master:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
5. On Sep 21 this year, Anil branched stable/phosphorus, but unlike all
the previous times, opendaylight/pom.xml's version was NOT updated:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
6. On Sep 24 this year, the first successful
distribution-merge-full-sulfur job run:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz,
happily doing:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (982 B at 18 kB/s)
7. On Sep 24 this year, run-of-the mill
distribution-merge-full-phosphorus ran:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz,
happily doing this:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
10. On Oct 24 distribution-merge-full-sulfur started failing:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz
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 (https://nexus.opendaylight.org/content/repositories/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.
Bye,
Robert
>
> For more information check this doc:
> https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
> <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html>
>
> BR/Luis
>
>> 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:
>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>> <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655>
>>
>> I have no skin in this particular game, sorry.
>>
>> Regards,
>> Robert
>>
>>
>>> On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via
>>> lists.opendaylight.org <http://lists.opendaylight.org>
>>> <http://lists.opendaylight.org <http://lists.opendaylight.org>>
>>> <sangwook.ha=verizon.com@...
>>> <mailto:sangwook.ha=verizon.com@...>
>>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>>> wrote:
>>> It appears that the versions in
>>> integration/distribution/opendaylight have not been updated, and
>>> some Jenkins jobs are failing: e.g.
>>> openflowplugin-csit-1node-sanity-only-sulfur
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/>>
>>> 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.
>>> Thanks,
>>> Sangwook
>>>
>
|
|
|
Re: integration/distribution version issues
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.
BR/Luis
toggle quoted messageShow quoted text
On Nov 17, 2021, at 1:18 AM, Robert Varga <nite@hq.sk> 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: https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
3. On Apr 3 this year, you changed the versioning scheme on stable/silicon to 14.0.0-SNAPSHOT: https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
4. On Apr 22 this year, Guillaume made a similar change on then-master: https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
5. On Sep 21 this year, Anil branched stable/phosphorus, but unlike all the previous times, opendaylight/pom.xml's version was NOT updated: https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
6. On Sep 24 this year, the first successful distribution-merge-full-sulfur job run: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz, happily doing:
Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz (266 MB at 28 MB/s)
Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (982 B at 18 kB/s) 7. On Sep 24 this year, run-of-the mill distribution-merge-full-phosphorus ran: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz, happily doing this:
Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz (266 MB at 28 MB/s)
Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (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: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
10. On Oct 24 distribution-merge-full-sulfur started failing: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
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: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz 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 (https://nexus.opendaylight.org/content/repositories/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.
Bye,
Robert
For more information check this doc: https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html>
BR/Luis
On Nov 16, 2021, at 9:08 PM, Robert Varga <nite@hq.sk <mailto:nite@hq.sk>> 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: https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655 <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655>
I have no skin in this particular game, sorry.
Regards,
Robert
On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via lists.opendaylight.org <http://lists.opendaylight.org> <http://lists.opendaylight.org <http://lists.opendaylight.org>> <sangwook.ha=verizon.com@lists.opendaylight.org <mailto:sangwook.ha=verizon.com@lists.opendaylight.org> <mailto:verizon.com@lists.opendaylight.org <mailto:verizon.com@lists.opendaylight.org>>> wrote:
It appears that the versions in
integration/distribution/opendaylight have not been updated, and
some Jenkins jobs are failing: e.g.
openflowplugin-csit-1node-sanity-only-sulfur
<https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/ <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/>>
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.
Thanks,
Sangwook
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
Regarding the version mismatch for the common release, what I meant was for the karaf version in 'opendaylight/pom.xml' and the other versions - for example, release tag '14.3.0' would have the karaf version of '0.14.3' in 'opendaylight/pom.xml' but the rest has '0.14.4'. So both '14.3.0' and 'release/silicon-sr4', when released, will have '0.14.4' as the version for all the artifacts, at least when looking at the repository.
Thanks, Sangwook
Looking at the release & version bump cycle, some of the steps may be simplified, and hopefully automated:
- For each release of managed projects, release & version bump, are done separately a few days apart - is there any reason why this cannot be done together? - For 'opendaylight/pom.xml' there are multiple manual steps: can steps 2 & 3 be merged & done automatically?
1) activate profiles for self-managed projects 2) release 3) update versions and deactivate profiles for self-managed projects (sometimes the version bump is done in two separate steps: the artifact/karaf & self-managed project)
And there are two different types of release tags - one for managed projects (e.g. release/silicon-sr3) and common release (14.3.0). The former does not update 'opendaylight/pom.xml' but the latter updates all the POM files. And this is confusing because all the versions except for 'opendaylight/pom.xml' have been bumped up by the time the release is made, and they have a version ahead of what the label says (e.g. for the tag '14.3.0' all the versions except for 'opendaylight/pom.xml' is '14.4.0').
Thanks, Sangwook On Wed, 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:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
3. On Apr 3 this year, you changed the versioning scheme on
stable/silicon to 14.0.0-SNAPSHOT:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
4. On Apr 22 this year, Guillaume made a similar change on then-master:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
5. On Sep 21 this year, Anil branched stable/phosphorus, but unlike all
the previous times, opendaylight/pom.xml's version was NOT updated:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
6. On Sep 24 this year, the first successful
distribution-merge-full-sulfur job run:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz,
happily doing:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (982 B at 18 kB/s)
7. On Sep 24 this year, run-of-the mill
distribution-merge-full-phosphorus ran:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz,
happily doing this:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
10. On Oct 24 distribution-merge-full-sulfur started failing:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz
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 (https://nexus.opendaylight.org/content/repositories/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.
Bye,
Robert
>
> For more information check this doc:
> https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
> <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html>
>
> BR/Luis
>
>> 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:
>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>> <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655>
>>
>> I have no skin in this particular game, sorry.
>>
>> Regards,
>> Robert
>>
>>
>>> On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via
>>> lists.opendaylight.org <http://lists.opendaylight.org>
>>> <http://lists.opendaylight.org <http://lists.opendaylight.org>>
>>> <sangwook.ha=verizon.com@...
>>> <mailto:sangwook.ha=verizon.com@...>
>>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>>> wrote:
>>> It appears that the versions in
>>> integration/distribution/opendaylight have not been updated, and
>>> some Jenkins jobs are failing: e.g.
>>> openflowplugin-csit-1node-sanity-only-sulfur
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/>>
>>> 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.
>>> Thanks,
>>> Sangwook
>>>
>
|
|
|
Re: [E] Re: [integration-dev] integration/distribution version issues
Looking at the release & version bump cycle, some of the steps may be simplified, and hopefully automated:
- For each release of managed projects, release & version bump, are done separately a few days apart - is there any reason why this cannot be done together? - For 'opendaylight/pom.xml' there are multiple manual steps: can steps 2 & 3 be merged & done automatically?
1) activate profiles for self-managed projects 2) release 3) update versions and deactivate profiles for self-managed projects (sometimes the version bump is done in two separate steps: the artifact/karaf & self-managed project)
And there are two different types of release tags - one for managed projects (e.g. release/silicon-sr3) and common release (14.3.0). The former does not update 'opendaylight/pom.xml' but the latter updates all the POM files. And this is confusing because all the versions except for 'opendaylight/pom.xml' have been bumped up by the time the release is made, and they have a version ahead of what the label says (e.g. for the tag '14.3.0' all the versions except for 'opendaylight/pom.xml' is '14.4.0').
Thanks, Sangwook
On Wed, 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:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95287
3. On Apr 3 this year, you changed the versioning scheme on
stable/silicon to 14.0.0-SNAPSHOT:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
4. On Apr 22 this year, Guillaume made a similar change on then-master:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/95789
5. On Sep 21 this year, Anil branched stable/phosphorus, but unlike all
the previous times, opendaylight/pom.xml's version was NOT updated:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/97551
6. On Sep 24 this year, the first successful
distribution-merge-full-sulfur job run:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz,
happily doing:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (982 B at 18 kB/s)
7. On Sep 24 this year, run-of-the mill
distribution-merge-full-phosphorus ran:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz,
happily doing this:
> Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz (266 MB at 28 MB/s)
> Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
> Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz
10. On Oct 24 distribution-merge-full-sulfur started failing:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz
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:
https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz
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 (https://nexus.opendaylight.org/content/repositories/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.
Bye,
Robert
>
> For more information check this doc:
> https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html
> <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html>
>
> BR/Luis
>
>> 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:
>> https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655
>> <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655>
>>
>> I have no skin in this particular game, sorry.
>>
>> Regards,
>> Robert
>>
>>
>>> On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via
>>> lists.opendaylight.org <http://lists.opendaylight.org>
>>> <http://lists.opendaylight.org <http://lists.opendaylight.org>>
>>> <sangwook.ha=verizon.com@...
>>> <mailto:sangwook.ha=verizon.com@...>
>>> <mailto:verizon.com@...
>>> <mailto:verizon.com@...>>> wrote:
>>> It appears that the versions in
>>> integration/distribution/opendaylight have not been updated, and
>>> some Jenkins jobs are failing: e.g.
>>> openflowplugin-csit-1node-sanity-only-sulfur
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/
>>> <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/>>
>>> 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.
>>> Thanks,
>>> Sangwook
>>>
>
|
|
|
Re: integration/distribution version issues
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: https://git.opendaylight.org/gerrit/c/integration/distribution/+/952873. On Apr 3 this year, you changed the versioning scheme on stable/silicon to 14.0.0-SNAPSHOT: https://git.opendaylight.org/gerrit/c/integration/distribution/+/956554. On Apr 22 this year, Guillaume made a similar change on then-master: https://git.opendaylight.org/gerrit/c/integration/distribution/+/957895. On Sep 21 this year, Anil branched stable/phosphorus, but unlike all the previous times, opendaylight/pom.xml's version was NOT updated: https://git.opendaylight.org/gerrit/c/integration/distribution/+/975516. On Sep 24 this year, the first successful distribution-merge-full-sulfur job run: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/2/console.log.gz, happily doing: Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz
Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.032546-1083.tar.gz (266 MB at 28 MB/s)
Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (982 B at 18 kB/s) 7. On Sep 24 this year, run-of-the mill distribution-merge-full-phosphorus ran: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1170/console.log.gz, happily doing this: Deploying the main artifact opendaylight-15.0.0-SNAPSHOT.tar.gz
Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz
Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/opendaylight-15.0.0-20210924.050736-1084.tar.gz (266 MB at 28 MB/s)
Uploading to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml
Uploaded to opendaylight-snapshot: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/opendaylight/15.0.0-SNAPSHOT/maven-metadata.xml (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: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-phosphorus/1322/console.log.gz10. On Oct 24 distribution-merge-full-sulfur started failing: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/149/console.log.gz11. On Nov 13 the last published opendaylight-15.0.0-SNAPSHOT expired in Nexus 12. On Nov 14 distribution-merge-full-sulfur started failing: https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/distribution-merge-full-sulfur/275/console.log.gz 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 (https://nexus.opendaylight.org/content/repositories/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. Bye, Robert For more information check this doc: https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html <https://docs.opendaylight.org/projects/integration-distribution/en/latest/add-project-distribution.html>
BR/Luis
On Nov 16, 2021, at 9:08 PM, Robert Varga <nite@hq.sk <mailto:nite@hq.sk>> 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: https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655 <https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655>
I have no skin in this particular game, sorry.
Regards,
Robert
On Tue, Nov 16, 2021 at 1:47 PM Sangwook Ha via lists.opendaylight.org <http://lists.opendaylight.org> <http://lists.opendaylight.org <http://lists.opendaylight.org>> <sangwook.ha=verizon.com@lists.opendaylight.org <mailto:sangwook.ha=verizon.com@lists.opendaylight.org> <mailto:verizon.com@lists.opendaylight.org <mailto:verizon.com@lists.opendaylight.org>>> wrote:
It appears that the versions in
integration/distribution/opendaylight have not been updated, and
some Jenkins jobs are failing: e.g.
openflowplugin-csit-1node-sanity-only-sulfur
<https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/ <https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-sanity-only-sulfur/>>
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.
Thanks,
Sangwook
|
|
|
