Forgot to mention that Jenkins has been removed from Shutdown mode, please re-trigger the jobs that failed.

The CentOS 7 builder/robot and devstack images are updated now on Jenkins prod now. We'll still require a few more images update, will continue tomorrow. Been a very long day here! Cheers. On Fri, Oct

Hello team: The issue has been resolved on Gerrit. However, we'll need to rebuild newer builders, which needs to be done manually. Please review the CR:

Hello all, Jenkins (releng and sandbox) has been put in shutdown mode temporarily to prevent triggering jobs. The Let's Encrypt root certificate expiry has caused an issue presently. We are working on

n 01/10/2021 09:30, Anil Belur wrote: Awesome, this is what we want to be aiming for and we will be establishing MRI project release process in terms of pipelines as soon as we get the green light

Hello all, I have installed Jenkins Blue Ocean on the ODL sandbox environment. Although Blue Ocean is installed on the Jenkins Sandbox environment, all existing CI jobs need to be migrated to

OK, I think I was the confused here :) After reading your mail, it makes sense to start testing MRI local distribution as you are doing

Ok. I've sent an email to TSC so the current phosphorus candidate can be approved Thanks

I think netconf devs would be less confused if you could share some writeup of how exactly is test execution wired across integration/test and releng/builder :) Please note that NETCONF is an MRI

I think netconf devs got confused on how our CSIT branches work, I do not see any CSIT job for phosphorous and therefore I do not think we are testing netconf in this

both #40 and #39 is having this issue ERROR: Build aborted. Can't trigger undefined projects. 1 of the below project(s) can't be resolved: > netconf-csit-1node-scale-max-devices-only-master

So the mri-test-phosphorus does not kick off of autorelease, but runs periodically. I have kicked off #40, but #39 should be accurate. Regards, Robert

Thanks Robert.. I've come up with this phosphorus release approval for TSC https://wiki.opendaylight.org/display/ODL/Phosphorus+Formal+Release+Approval but I couldn't find the right mri test ... it

Okay, so we have one remaining issue in BGPCEP, but after spending today trying to make sense of what is going on, it is not a regression, just shifted timing in code. It may have been detected

Okay, I think I found the culprint. A fixed bgpcep should be out in about two hours or so and should be reflect in next AR build. Bye, Robert

Alright, this looks like a pccmock

Yeah, it's three test cases, all of them are PCEP-related. They are failing reliably, which seems to indicate a systemic problem. I'll try to see if I can debug/repro it tomorrow. We might punt to

It seems that we are still having Bgp and pcep issues but are they all critical ? Or can we fix them later so we can release phosphorus ?

Hi Robert: The jjb-merge job failed since a new branch is added and the CR changes a lots of job configs. This translates to updating all the job configs on Jenkins and requires more time to

it seems that the issue has been fixed by LF IT so are we good to pick up Phosphorus AR #216 integration #174 is showing some BGPCEP failed test