On 28/08/2019 06:36, Anil Belur wrote:
> Greetings all,

Hello Anil,

> Going forward, we'll need to configure the smart proxy on our the
> environment to sync and publish artifacts onto Central. Also, we'll need
> to ensure this is done on priority so that ODL's staging repositories
> for the upcoming releases don't get purged.

Right, and as with my various hats on, let's make this happen as soon as
possible. We are *long* overdue with a Central SR release, it just Must
Work(tm).

With my MRI hats on, experience shows we cannot get rid of ODL Nexus, so
if the release is driven by ODL Nexus and Central is just a recipient of
promoted org.opendaylight.* artifacts, all is good.

+1 on executing on this right now.

Regards,
Robert

On Thu, Aug 29, 2019 at 1:15 AM Robert Varga <nite@...> wrote:

On 28/08/2019 06:36, Anil Belur wrote:
> Greetings all,

Hello Anil,

> Going forward, we'll need to configure the smart proxy on our the
> environment to sync and publish artifacts onto Central. Also, we'll need
> to ensure this is done on priority so that ODL's staging repositories
> for the upcoming releases don't get purged.

Right, and as with my various hats on, let's make this happen as soon as
possible. We are *long* overdue with a Central SR release, it just Must
Work(tm).

With my MRI hats on, experience shows we cannot get rid of ODL Nexus, so
if the release is driven by ODL Nexus and Central is just a recipient of
promoted org.opendaylight.* artifacts, all is good.

+1 on executing on this right now.

Regards,
Robert

Hello:

Taking into considering that we are in the mids of 2 releases and staging repositories are getting randomly removed on OSS,

can we remove/drop older staging repos on OSS, retaining the one from #222 for Neon SR2 and #170 for Sodium release.  

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-neon-mvn35-openjdk8/222/staging-repo.txt.gz

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk8/170/staging-repo.txt.gz

Thanks,

Anil

On Thu, Aug 29, 2019 at 8:32 AM Anil Belur <abelur@...> wrote:

On Thu, Aug 29, 2019 at 1:15 AM Robert Varga <nite@...> wrote:

On 28/08/2019 06:36, Anil Belur wrote:
> Greetings all,

Hello Anil,

> Going forward, we'll need to configure the smart proxy on our the
> environment to sync and publish artifacts onto Central. Also, we'll need
> to ensure this is done on priority so that ODL's staging repositories
> for the upcoming releases don't get purged.

Right, and as with my various hats on, let's make this happen as soon as
possible. We are *long* overdue with a Central SR release, it just Must
Work(tm).

With my MRI hats on, experience shows we cannot get rid of ODL Nexus, so
if the release is driven by ODL Nexus and Central is just a recipient of
promoted org.opendaylight.* artifacts, all is good.

+1 on executing on this right now.

Regards,
Robert

Hello:

Taking into considering that we are in the mids of 2 releases and staging repositories are getting randomly removed on OSS,

can we remove/drop older staging repos on OSS, retaining the one from #222 for Neon SR2 and #170 for Sodium release.  

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-neon-mvn35-openjdk8/222/staging-repo.txt.gz

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-sodium-mvn35-openjdk8/170/staging-repo.txt.gz

Thanks,

Anil

As discussed with Robert on the IRC, we are disabling the @daily cron timers for _all_ the maven-stage jobs on ODL Jenkins, this to address the OSS Nexus instability.

The change needs to be merged:

https://git.opendaylight.org/gerrit/c/releng/builder/+/84058 

Next thing, on the list is to drop/remove all staging repositories that are not marked as RC for the upcoming releases.

Thanks,

Anil