Operating System: All
Platform: All

Is this issue related to integration or is it a problem with other projects?

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

Which projects from the list you do not build in autorelease so I really have to take a look?

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...

(In reply to Luis Gomez from comment #2)
> Which projects from the list you do not build in autorelease so I really
> have to take a look?

Hi Luis,

VTN and NIC projects are not built in autorelease due to the AD-SAL dependencies of VTN (VTN-87).
If we temporarily remove VTN dependencies from NIC, I think we can build NIC successfully in autorelease.
But anyway VTN build does not work in autorelease.

I would like to discuss how to deal with this issue wit you.

For sfc I just sent mail.

For vtn/nic, Hideyuki, when do you expect to have vtn back working? if this is not happening soon we can:

• nic: remove vtn feature dependency in the project itself, by doing that we can include nic back in autorelease.

• vtn: remove temporarily from int/distribution.

BR/Luis

By the way, does the autorelease job tolerate unit test failures? Bgpcep project currently suffers those due to MDSAL-116.
And if it does not tolerate those, does it exit early like

-merge and

-integration jobs do?

Both NIC and VTN are removed from autorelease.

https://git.opendaylight.org/gerrit/gitweb?p=releng/autorelease.git;a=blob;f=pom.xml;

(In reply to Luis Gomez from comment #5)
> For sfc I just sent mail.
>
> For vtn/nic, Hideyuki, when do you expect to have vtn back working? if this
> is not happening soon we can:
>
> - nic: remove vtn feature dependency in the project itself, by doing that we
> can include nic back in autorelease.
>
> - vtn: remove temporarily from int/distribution.
>
> BR/Luis

Hi Luis,

It does not happen soon.
I think we can run VTN build in autorelease from around the end of this month.

Therefore, let's take the approach you suggested.
I'll work on removing VTN feature dependency in NIC project.
After that work is done, I think we can include nic back in autorelease.
And, also we remove temporarily from the int/distribution.

The following patch disabled build of VTN Renderer module in NIC project.
https://git.opendaylight.org/gerrit/#/c/30013/

Now, I think we can include nic back in autorelease.

The following patch adds NIC back into autorelease.
https://git.opendaylight.org/gerrit/#/c/30016/ (not merged yet)

The following patch removes VTN from the int/distribution.
https://git.opendaylight.org/gerrit/#/c/30014/ (not merged yet)

These patches are needed to fix the INTEGRAT-44.
I'm waiting for reviewers for them.

I have noticed we have (at least) two bugs for the same issue.