I have retriggered the job, as the OVSDB/OFP test cases failed with: i.e. instance limits, again :( Bye, Robert

Hello Luis, everyone, patch https://git.opendaylight.org/gerrit/c/integration/distribution/+/95655 (Change Silicon version to 14.0.0) broke both these jobs: https://jenkins.opendaylight.org/releng/job

Hello, while resolving docs.opendaylight.org links to MRI projects, I have come across a slight problem with having versions propagated. Since MRI projects produce versions rather more often than thei

Hey Anil, Yes, a database export is what I was asking for, sorry for not being clear :) Thanks, Robert

Hello, Can we export the data from that instance and have it archived somewhere reachable, please? Thanks, Robert

Well, at the end of the day, there is another question: why are we even building these from sources? Regards, Robert

This is building ovs-2.8.1, while it should really be upgraded to 2.8.11. These are very simple build errors and should take just a few minutes to resolve to anyone familiar with building autotools-en

Hello again, sorry, for self-reply, but as it happens ... [snip] ... we just got hit by this. [snip] A case in point: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/yangtools-maven-verify-

Hello Anil, Understood. At the end of the day, though, we have only a few classes of jobs and there is a ton of commonalities between them. I do not believe this is the case for OpenDaylight jobs. For

We are not. We are picking candidates for SR3 -- and https://jenkins.opendaylight.org/releng/job/autorelease-release-aluminium-mvn35-openjdk11/360/ is good as any :) Regards, Robert

Hello everyone, as the (still current) failure to start Jenkins jobs shows, our current way of integrating with external dependencies (global-jjb) is beyond fragile. The way our jobs work is that: 1)

Yeah, and now all of jenkins has ground to a halt: https://jenkins.opendaylight.org/releng/ This is a real blocker now :( Regards, Robert

This is actually mis-aligned simply because jsonrpc-1.7.4 still references Magnesium SR3: Bye, Robert

Precisely. It should be okay now. Sorry it took this long :( Regards, Robert

Ah, sorry. Either fix will do. The odlparent backport is being pushed out. It might be worthwhile to do the includeArtifacts on master at some point also, as it could cut down on build time: (that's l

nite@nitebug : ~/odl/ovsdb on $ mvnDebug clean install -rf :library then attaching Eclipse debugger, breaking on IllegalArgumentException being thrown ends up with a stack trace which points to: META-

I observed the same thing with IT-20151 -- just the headline, nothing else. Regards, Robert

+correct email

[snip] This is across all releases, I just updated the ticket and raised it to blocker, as it does block any attempt to release anything. I have attached known-good and known-bad console.log and the '

Well, we fixed feature packaging in distribution (i.e. we now include features-controller-testing and others). Also, validate-autorelease triggers only when pom.xmls are modified I think, hence it is