This will take care of integration and distribution remaining changes for neon:

https://git.opendaylight.org/gerrit/#/c/75151/

BR/Luis

On Aug 11, 2018, at 6:07 AM, Robert Varga <nite@...> wrote:

On 10/08/18 00:05, Michael Vorburger wrote:

On Thu, Aug 9, 2018 at 11:59 PM Michael Vorburger <vorburger@...
<mailto:vorburger@...>> wrote:

   On Thu, Aug 9, 2018 at 4:55 PM Anil Belur
   <abelur@... <mailto:abelur@...>> wrote:

       Hello Everyone,

       We have performed branch cutting today with the master branch
       blocked. The work is complete and the master branch (Neon) is
       now open for development again. 

       Note: A reminder for projects to rebase their existing master
       branch patches to ensure they are building against the post
       version bumped versions of code base.


   Thank you! But the distribution jobs are still broken
   (e.g. https://jenkins.opendaylight.org/releng/job/infrautils-distribution-check-neon/2/console)
   - is someone looking into and going to fix those? Anil, not
   neccessarily looking at you - I'm guessing integration/distribution
   folks will know what where still needs bumping versions?


erm, oups, no wait, hit Send too early - perhaps more importantly than
distribution failures: at least genius is still completely broken
currently,
see https://jenkins.opendaylight.org/releng/job/genius-maven-verify-neon-mvn35-openjdk8/1/consoleFull
... I'm guessing we did not yet run deploy jobs on all projects (in
order of the dependency tree) to populate Nexus, yet?

Everything is go, bu archetypes need
https://git.opendaylight.org/gerrit/#/c/75136/ and branching...

Regards,
Robert

_______________________________________________
dev mailing list
dev@...
https://lists.opendaylight.org/mailman/listinfo/dev

On Mon, Aug 13, 2018 at 5:50 AM Luis Gomez <ecelgp@...> wrote:

This will take care of integration and distribution remaining changes for neon:

https://git.opendaylight.org/gerrit/#/c/75151/

cool, now we just need to get autorelease to actually pass again... ;-) I'm still, right now, seeing various failures on https://jenkins.opendaylight.org/releng/job/genius-validate-autorelease-neon/8/console from the following projects:

* lispflowmapping

* bgpcep

* netconf

* controller

I'll see if I can help with controller myself ASAP - hoping bgpcep and lispflowmapping and netconf fix their failures in autorelease...

BR/Luis

On Aug 11, 2018, at 6:07 AM, Robert Varga <nite@...> wrote:

On 10/08/18 00:05, Michael Vorburger wrote:

On Thu, Aug 9, 2018 at 11:59 PM Michael Vorburger <vorburger@...
<mailto:vorburger@...>> wrote:

   On Thu, Aug 9, 2018 at 4:55 PM Anil Belur
   <abelur@... <mailto:abelur@...>> wrote:

       Hello Everyone,

       We have performed branch cutting today with the master branch
       blocked. The work is complete and the master branch (Neon) is
       now open for development again. 

       Note: A reminder for projects to rebase their existing master
       branch patches to ensure they are building against the post
       version bumped versions of code base.


   Thank you! But the distribution jobs are still broken
   (e.g. https://jenkins.opendaylight.org/releng/job/infrautils-distribution-check-neon/2/console)
   - is someone looking into and going to fix those? Anil, not
   neccessarily looking at you - I'm guessing integration/distribution
   folks will know what where still needs bumping versions?


erm, oups, no wait, hit Send too early - perhaps more importantly than
distribution failures: at least genius is still completely broken
currently,
see https://jenkins.opendaylight.org/releng/job/genius-maven-verify-neon-mvn35-openjdk8/1/consoleFull
... I'm guessing we did not yet run deploy jobs on all projects (in
order of the dependency tree) to populate Nexus, yet?

Everything is go, bu archetypes need
https://git.opendaylight.org/gerrit/#/c/75136/ and branching...

archetypes https://git.opendaylight.org/gerrit/#/c/75136/ merged. How come this project was missed before? Should it be in autorelease? (It currently is not, according to https://github.com/opendaylight/releng-autorelease.)

Anil, will you do the branching on archetypes? Does it need to be added somewhere to not be forgotten next time?

On 13/08/18 14:06, Anil Belur wrote:
>
>     https://git.opendaylight.org/gerrit/#/c/75151/
>
>
> cool, now we just need to get autorelease to actually pass again... ;-)
> I'm still, right now, seeing various failures
> on https://jenkins.opendaylight.org/releng/job/genius-validate-autorelease-neon/8/console
> from the following projects:
>

00:04:11.596 Entering 'mdsal'
00:04:11.607 mdsal 3e5d53eefead8a109f72b9d658432050d01e8cf1 Validate

mdsal is not getting updated to the proper commit, which should be
3346408b80c3dd860d42f18469c7e35aa01cfee3

On Mon, Aug 13, 2018 at 2:09 PM Robert Varga <nite@...> wrote:

On 13/08/18 14:06, Anil Belur wrote:
>
>     https://git.opendaylight.org/gerrit/#/c/75151/
>
>
> cool, now we just need to get autorelease to actually pass again... ;-)
> I'm still, right now, seeing various failures
> on https://jenkins.opendaylight.org/releng/job/genius-validate-autorelease-neon/8/console
> from the following projects:
>

00:04:11.596 Entering 'mdsal'
00:04:11.607 mdsal 3e5d53eefead8a109f72b9d658432050d01e8cf1 Validate

mdsal is not getting updated to the proper commit, which should be
3346408b80c3dd860d42f18469c7e35aa01cfee3

I've hopefully fixed it with https://git.opendaylight.org/gerrit/#/c/75167/

by doing what I've documented on https://wiki.opendaylight.org/view/RelEng/Autorelease/Maintenance_Guide#Fix_up_broken_autorelease_which_fell_behind (which can perhaps be improved)

but it begs the quesiton why we have to manually do this?