Actually, the logs are there: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/openflowplugin-csit-1node-flow-services-all-aluminium/48/ but the link is not there in jenkins like

Has anything changed lately in the infra so that no log is stored

It may be short, but we can at least catch up on release status. Thanks, JamO

It's not always obvious, but you have to dig through the console log to see what's wrong. Here's what I found: [ERROR] Non-resolvable import POM: Could not find artifact

This combination is always wrong in a production artifact's pom.xml. Bye, Robert

Thanks Robert for your explanation. I cloud see below changes are there in the GENIUS project where as netvirt module pom.xml we didn't not changed the same. Is this root cause of the failure?

[snip] test-jar should never make it to the distribution, one of your patches has introduced a wrong dependency (i.e. not scope=test). Bye, Robert

+Robert Varga , @Robert Varga, We request your help on resolving reported problem in below email. We have tried installing following feature in the multi-patch integration distribution and it works

Hi All, We are trying to bring-up the integrated karaf distribution[0] locally(Windows Environment) which has been generated for MDSAL-APIs migration un-merged reviews[1] and it throws run-time

Hi Karthika, What job is this? if it's in the sandbox, that's expected. The sandbox does not have permission to upload to nexus. Thanks, JamO On 4/17/20 3:29

Hi Jamo/Luis, I triggered a multipatch build and the build is passing. But the generated distribution is not getting copied properly. How do we resolve this? 15:31:40 [ERROR] Failed to execute

The OpenFlow Plugin project page needs to be updated. :) Best, Casey Cain Technical Program Manager / Community Architect Linux Foundation _________________ IRC: CaseyLF WeChat: okaru6 Voice:

This is all great for those of us already receiving emails and paying attention, but if you are new to OpenDaylight and want to get the attention of say, openflowplugin (as an

Yes - actually I was in favor of that alternative. However since it had already passed with only 2 lists instead of 3 or 4, I decided to skip that particular vote :). We can talk about it in the TSC

In advance of this change, I put in the Project template on the wiki to indicate either app-dev or kernel-dev. As Projects migrate to the new wiki, if they use the template that I provided, they

Hi, Jamo. I sent out the mapping of mailing lists as part of the migration. Currently, projects that are considered "Kernel" are all forwarded to kernel-dev. All other mailing lists (not including

I do not know if it too late for this but I also think it would have been better to separate in kernel, plugins and apps.

I agree with you. It should be there somewhere central. It should be also on each project’s wiki.

Yeah, I can look up the old emails too. My question comes from the POV of a new person and how they are supposed to know where to send an email? Thanks, JamO

Jamo, In the email below are listed the projects in the kernel mailing list. The remaining projects should be in the app-dev mailing list. Abhijit ---------- Forwarded message --------- From: Casey