I tracked this down. It was caused by the upgrade to global-jjb v0.21.0 patch: https://git.opendaylight.org/gerrit/73173 After inspecting the commit log of global-jjb for versions between v0.19.2

Thanks for the clarification, but it was rolled out

We definitely dropped the ball here, this change should have been better communicated to the community before it was rolled out. Sorry about that. Regards, Thanh

Hi Robert, That was caused by this patch https://git.opendaylight.org/gerrit/71087 which was merged 9 weeks ago. Which was a result of this Jira https://jira.opendaylight.org/browse/RELENG-97 when we

Could this also explain why verify-javadoc jobs are suddenly using mvn35 instead of mvn33 ? Regards, Robert

I think this is happening every 1-2 months lately. JamO

Seems like a breaking change for ODL's JJB users. We should document this, update the example jenkins.ini.example in releng/builder and notify the community when a change like this is requires users

top posting TL;DR upgrade to jenkins-job-builer 2.0.10+ add "retain_anchors=True' to your --conf file JamO

Hello all, Initially, ./builder/jjb/releng-views.yaml was common place holder for manging project specific views on Jenkins through code because JJB versions earlier to 2.0.10 did not allow

Hello integration-dev (please cross-post if this is not the right list for this kind of problem?), The https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-publish-fluorine/ jobs are

Hey, The problem here is that <<: *releng_view_common is referencing to mapping located in jjb/releng-views.yaml -> &releng_view_common as far as I know we cannot reference to different file, so

Tomas was also indicating the same issue. I don't have much clue about this -view section. Tomas was asking to move this section to releng-views, but Anil told the current approach looks good

Hi all, (is there a serviceutils list to use, or just genius, or what?) Anyway, the -view section in the serviceutils.yaml was borking my attempt to push a job to the sandbox. this removes it, and

Hello. Anyone know the reason for the following auto-release failure. Something ia referencing yang-test-plugin but the patch removed it as part of removing config-system code; 23:15:18 [ERROR]

netvirt: https://meetings.opendaylight.org/opendaylight-netvirt/2018/netvirt_weekly_06_19_18/opendaylight-netvirt-netvirt_weekly_06_19_18.2018-06-19-15.01.html kernel: https://meetings.opendaylight

https://git.opendaylight.org/gerrit/73264 should get distribution working again while we fix serviceutils.

Michael, Trying to see where the problem is. If taking more time, let us merge the revert patch :https://git.opendaylight.org/gerrit/#/c/73264/ And we will fix things and put the

https://git.opendaylight.org/gerrit/#/c/73247/ failed again, but it went further - I think; now "just" failing with an SFT problem in serviceutils? (Before it fell over somewhere earlier.)

First auto merge failed, but subsequent remerge went through fine. Should likely work now.

my guess is that serviceutils merge job only just passed 90m ago, and that was after your distro-check ran and failed to find their artifacts on nexus. I see the artifacts there now with a recent