integration-dev@lists.opendaylight.org

Home Messages Hashtags Subgroups

Messages

Between

and

Re: [tsc][infrastructure] Backend network issues

The cloud provider has resolved the issue for now, I'll continue monitoring the services for some time. If you notice job failures because of timeouts, please retrigger the jobs or run 'recheck' ||

By Anil Belur · #14523 ·

[tsc][infrastructure] Backend network issues

Hello all, We presently have backend network issues and are working with the Cloud provider to get this resolved. Jenkins jobs logs would network timeout errors while resolving dependencies. Will

By Anil Belur · #14522 ·

[tsc][release][integration-dev] Branch stable/aluminium - locked/EOL

Hello all, Since OpenDaylight Phosphorus is released, the stable/aluminium branch will be locked on Gerrit and no longer available for development. All Jenkins CI jobs for the 'stable/aluminium' on

By Anil Belur · #14521 ·

Re: [tsc][releng][integration] Jenkins pipelines with Blue Ocean

So, pipelines live in a .jenkinsfile that resides at the root level of a repository. We will still need JJB to stub in the reading of that file which then defines _all_ the pipelines for a given

By Andrew Grimberg · #14520 ·

Re: [OpenDaylight TSC] [tsc][Infrastructure] Jenkins in shutdown mode

Ack, everything seems to be working again. Thanks, Robert

By Robert Varga · #14519 ·

Re: [OpenDaylight TSC] [tsc][Infrastructure] Jenkins in shutdown mode

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

By Anil Belur · #14518 ·

Re: [OpenDaylight TSC] [tsc][Infrastructure] Jenkins in shutdown mode

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

By Anil Belur · #14517 ·

Re: [tsc][Infrastructure] Jenkins in shutdown mode

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:

By Anil Belur · #14516 ·

[tsc][Infrastructure] Jenkins in shutdown mode

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

By Anil Belur · #14515 ·

Re: [tsc][releng][integration] Jenkins pipelines with Blue Ocean

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

By Robert Varga · #14514 ·

[tsc][releng][integration] Jenkins pipelines with Blue Ocean

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

By Anil Belur · #14513 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Luis Gomez · #14512 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Daniel de la Rosa · #14511 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Robert Varga · #14510 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Luis Gomez · #14509 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Daniel de la Rosa · #14508 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Robert Varga · #14507 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Daniel de la Rosa · #14506 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Robert Varga · #14505 ·

Re: [release] [releng][TSC] phosphorus release status - master branch has been locked

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

By Robert Varga · #14504 ·

161 - 180 of 14683

Home Hashtags Subgroups Terms