https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/RELENG-21 releng <p>When merging patch: org.opendaylight.netconf:features-restconf:xml:features:1.3.0-SNAPSHOT into netconf project, pretty much each pom.xml file was changed.</p> <p>Jenkins merge job for this project, just published a few of them to nexus, which resulted in broken pom files for netconf project (referencing not existing artefacts, versions, etc).</p> <p>If you look into<br/> <a href="https://jenkins.opendaylight.org/releng/job/netconf-merge-beryllium/46/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/netconf-merge-beryllium/46/</a></p> <p>you could see that most of projects we're build but only a slew of them were uploaded to nexus.</p> <p>Operating System: All<br/> Platform: All</p> RELENG-21

Jenkins Merge jobs does not deploy all builded artefacts

Bug Resolved Done Unassigned Tony Tkacik Tue, 15 Sep 2015 07:37:06 +0000 Tue, 27 Feb 2018 15:45:21 +0000 Tue, 27 Feb 2018 15:45:21 +0000 unspecified Jenkins Job Builder 0 1 <p>Attaching log file for historical recording.</p> <p>Attachment netconf-merge-46.zip has been added with description: netconf-merge-46</p> <p>This may have been an intermittent issue since I see now that future netconf-merge jobs successfully deployed all artifacts. So we'll keep this bug on watch if it happens again.</p> <p>I'm not sure why this would happen but I have seen once in awhile issues with Jenkins' Maven listener which sometimes gets disconnected from the build and loses track of the build. While Maven successfully completes the build Jenkins incorrectly detects which modules were built and reports incorrectly. This is not a JJB Template issue but likely a bug in Jenkins' Maven plugin.</p> <p>Thanks for quick analysis, but honestly do not know better place to keep that bug open for future reference.</p> <p>(In reply to Tony Tkacik from comment #3)<br/> &gt; Thanks for quick analysis, but honestly do not know better place to keep<br/> &gt; that bug open for future reference.</p> <p>Leaving it here is fine.</p> <p>I believe this is no longer an issue and this is a very old bug.</p> Development External issue ID 4312 External issue URL Rank 0|i01m27: