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/INTDIST-44 integration-distribution <p><a href="https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-daily-beryllium/278/console" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-daily-beryllium/278/console</a></p> <p><span class="error">&#91;ERROR&#93;</span> Failed to execute goal on project features-integration-index: Could not resolve dependencies for project org.opendaylight.integration:features-integration-index:jar:0.4.0-Daily-v201511190023</p> <p>Operating System: All<br/> Platform: All</p> INTDIST-44

features-integration-index could not resolve dependencies

Bug Resolved Duplicate Unassigned A H Thu, 19 Nov 2015 17:31:52 +0000 Fri, 20 Oct 2017 10:24:52 +0000 Sat, 19 Nov 2016 00:52:12 +0000 unspecified Build 0 4 <p>Is this issue related to integration or is it a problem with other projects?</p> <p>The following artifacts could not be resolved: org.opendaylight.nic:features-nic:xml:features:1.1.0-Daily-v201511190023, org.opendaylight.sfc:features-sfc-sb-rest:xml:features:0.2.0-Daily-v201511190023, org.opendaylight.sfc:features-sfclisp:xml:features:0.2.0-Daily-v201511190023, org.opendaylight.sfc:features-sfcofl2:xml:features:0.2.0-Daily-v201511190023, org.opendaylight.sfc:features-sfc-ovs:xml:features:0.2.0-Daily-v201511190023, org.opendaylight.sfc:features-sfc-netconf:xml:features:0.2.0-Daily-v201511190023, org.opendaylight.vtn:features-vtn-manager:xml:features:0.4.0-Daily-v201511190023: Could not find artifact org.opendaylight.nic:features-nic:xml:features:1.1.0-Daily-v201511190023 in opendaylight-mirror</p> <p>Which projects from the list you do not build in autorelease so I really have to take a look?</p> <p>Actually the other way around, the projects that you do not build I do not have to take a look, just remove them from integration...</p> <p>(In reply to Luis Gomez from comment #2)<br/> &gt; Which projects from the list you do not build in autorelease so I really<br/> &gt; have to take a look?</p> <p>Hi Luis,</p> <p>VTN and NIC projects are not built in autorelease due to the AD-SAL dependencies of VTN (<a href="https://jira.opendaylight.org/browse/VTN-87" title="VTN Manager depends on missing dependencies" class="issue-link" data-issue-key="VTN-87"><del>VTN-87</del></a>).<br/> If we temporarily remove VTN dependencies from NIC, I think we can build NIC successfully in autorelease.<br/> But anyway VTN build does not work in autorelease.</p> <p>I would like to discuss how to deal with this issue wit you.</p> <p>For sfc I just sent mail.</p> <p>For vtn/nic, Hideyuki, when do you expect to have vtn back working? if this is not happening soon we can:</p> <ul class="alternate" type="square"> <li>nic: remove vtn feature dependency in the project itself, by doing that we can include nic back in autorelease.</li> </ul> <ul class="alternate" type="square"> <li>vtn: remove temporarily from int/distribution.</li> </ul> <p>BR/Luis</p> <p>By the way, does the autorelease job tolerate unit test failures? Bgpcep project currently suffers those due to <a href="https://jira.opendaylight.org/browse/MDSAL-116" title="Binding Dom Codec : ClassCastException when EncapsulatedValueCodec deserialize BinaryType" class="issue-link" data-issue-key="MDSAL-116"><del>MDSAL-116</del></a>.<br/> And if it does not tolerate those, does it exit early like </p> {project}-verify sub-jobs do, or does it realize UNSTABLE state only after archiving artifacts (but before deploying to Nexus) as {project} <p>-merge and </p> {project} <p>-integration jobs do?</p> <p>Both NIC and VTN are removed from autorelease.</p> <p><a href="https://git.opendaylight.org/gerrit/gitweb?p=releng/autorelease.git;a=blob;f=pom.xml" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/gitweb?p=releng/autorelease.git;a=blob;f=pom.xml</a>;</p> <p>(In reply to Luis Gomez from comment #5)<br/> &gt; For sfc I just sent mail.<br/> &gt; <br/> &gt; For vtn/nic, Hideyuki, when do you expect to have vtn back working? if this<br/> &gt; is not happening soon we can:<br/> &gt; <br/> &gt; - nic: remove vtn feature dependency in the project itself, by doing that we<br/> &gt; can include nic back in autorelease.<br/> &gt; <br/> &gt; - vtn: remove temporarily from int/distribution.<br/> &gt; <br/> &gt; BR/Luis</p> <p>Hi Luis,</p> <p>It does not happen soon.<br/> I think we can run VTN build in autorelease from around the end of this month.</p> <p>Therefore, let's take the approach you suggested.<br/> I'll work on removing VTN feature dependency in NIC project.<br/> After that work is done, I think we can include nic back in autorelease.<br/> And, also we remove temporarily from the int/distribution.</p> <p>The following patch disabled build of VTN Renderer module in NIC project.<br/> <a href="https://git.opendaylight.org/gerrit/#/c/30013/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/30013/</a></p> <p>Now, I think we can include nic back in autorelease.</p> <p>The following patch adds NIC back into autorelease.<br/> <a href="https://git.opendaylight.org/gerrit/#/c/30016/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/30016/</a> (not merged yet)</p> <p>The following patch removes VTN from the int/distribution.<br/> <a href="https://git.opendaylight.org/gerrit/#/c/30014/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/30014/</a> (not merged yet)</p> <p>These patches are needed to fix the <a href="https://jira.opendaylight.org/browse/INTDIST-44" title="features-integration-index could not resolve dependencies" class="issue-link" data-issue-key="INTDIST-44"><del>INTEGRAT-44</del></a>.<br/> I'm waiting for reviewers for them.</p> <p>I have noticed we have (at least) two bugs for the same issue.</p> Duplicate INTDIST-41 Development External issue ID 4653 External issue URL Rank 0|i01lkn: