Thanks for the answer.

If so, on which non-SNAPSHOT versions am I supposed to depend on ? Is 1.2.6 okay ?

 

Cf previous thread at https://lists.opendaylight.org/pipermail/tsc/2019-January/010942.html

I didn’t have any clue on either

https://docs.opendaylight.org/projects/integration-distribution/en/latest/platform-versions.html

or

https://wiki.opendaylight.org/view/Neon_platform_upgrade#MD-SAL_Impacts

 

 

 

From: Tom Pantelis [mailto:tompantelis@...]
Sent: mardi 19 février 2019 15:37
To: LAMBERT Guillaume TGI/OLN
Cc: Luis Gomez; <ylhsieh@...>; tsc@...; release@...
Subject: Re: [release] SM projects status

 

 

 

On Tue, Feb 19, 2019 at 5:16 AM <guillaume.lambert@...> wrote:

Hi all

Luis, I created a TransportPCE stable/neon branch yesterday with a config that was working last week..
But I got a Jenkins build failure because of obsolete poms. It appears that Mdsal binding models 1.2.6-SNAPSHOT were removed yesterday and replaced by 1.2.7-SNAPSHOT ones.

 

The mdsal ;project is release integrated (or whatever the official term is) so you're not supposed to depend on snapshot versions.

 

 

I fixed the poms in this change https://git.opendaylight.org/gerrit/#/c/80373/ but the branch was locked... I believe this is an error since branch locks should probably not apply to SM projects.
So I had no other choices than to delete the branch and recreate it from master to have a working pom configuration.
Now the stable/neon branch builds.
However, I believe the netconf REST API has evolved and this causes many functional tests unexpected failures. We are investigating that.
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/transportpce-tox-verify-neon/95/tox/py27/
(to compare with before Neon bump https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/transportpce-tox-verify-sodium/5/tox/py27/ )

Best regards
Guillaume

_________________________________________________________________________________________________________________________

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.