Operating System: All
Platform: All

I've investigated this failure.

The reason of the failure is that the VTN project is depending AD-SAL artifacts which does not exist anymore in the master branch of the controller project.
In Beryllium, VTN project plans to remove that dependency by the M4 (11/12).

Therefore, I think we should temporarily remove the VTN project from the autorelease job to avoid that build failure.
Otherwise, we need to ask the controller project to revert the following patch which deleted the AD-SAL artifacts to get back the artifacts.
https://git.opendaylight.org/gerrit/#/c/18740/

Note:
Basically, VTN builds on the master branch works fine.
https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-integration-beryllium/

That's because VTN builds can use SNAPSHOT artifacts of the AD-SAL from the NEXUS repository.
For example, org.opendaylight.controller:sal:jar:0.10.0-SNAPSHOT is available at the following location.
https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/controller/sal/0.10.0-SNAPSHOT/

However, since the autorelease job does not use these SNAPSHOT artifacts at the NEXUS repository, the build failure occurred.

This patch which temporarily disables VTN from autorelease should be reverted when this bug is resolved:

https://git.opendaylight.org/gerrit/28022/

Hideyuiki,
you could use last released AD-SAL components, which are Lithium-based instead of Be SNAPSHOTs (which as you pointed out does not exists anymore).

> you could use last released AD-SAL components, which are Lithium-based instead of Be SNAPSHOTs

Oh, I forgot to comment on this.
1. I do not think Beryllium autorelease job has access to Lithium released artifacts.
2. Even if it has, I do not think it is desirable to pull different version of third party dependecies. For example Netty has version 4.0.26.Final in Lithium [0], but 4.0.30.Final in current Beryllium [1].

Other than that, it may work as emergency measure for now.

[0] https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/controller/features-base/1.5.2-Lithium-SR2/features-base-1.5.2-Lithium-SR2-features.xml

[1] https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/controller/features-config/0.4.0-SNAPSHOT/features-config-0.4.0-20151103.215908-326-features.xml

According to [1] VTN will remove AD-SAL by 2015-12-03.

[1] https://lists.opendaylight.org/pipermail/release/2015-November/004455.html

Hideyuki, any updates on this other than the one I link from comment 5?

Please keep us posted so we can re-enable VTN in autorelease.

(In reply to Thanh Ha from comment #6)
> Hideyuki, any updates on this other than the one I link from comment 5?
>
> Please keep us posted so we can re-enable VTN in autorelease.

It's not yet done.
I think we can completely delete AD-SAL dependencies by the end of this month.

Just for your information, we've merged a huge patch for the migration yesterday. The most work for the migration was completed in the patch. That was really heavy task.
https://git.opendaylight.org/gerrit/#/c/30033/
The day is really close.

I did some investigation. Something like this is still needed: https://git.opendaylight.org/gerrit/30495

(In reply to Vratko Polák from comment #8)
> I did some investigation. Something like this is still needed:
> https://git.opendaylight.org/gerrit/30495

Thank you for your investigation.

Our work for removing AD-SAL dependencies has not been completed yet.

The following patch is removing AD-SAL dependencies.
https://git.opendaylight.org/gerrit/#/c/30476/
Of course, this patch include your change.

We are reviewing this patch.
I think we would merge the patch soon.

We've completed the removal of the AD-SAL dependencies from VTN on the master branch (for Beryllium).

https://git.opendaylight.org/gerrit/#/c/30476/

Now, VTN on the master branch does not depend on AD-SAL anymore.

(In reply to Thanh Ha from comment #2)
> This patch which temporarily disables VTN from autorelease should be
> reverted when this bug is resolved:
>
> https://git.opendaylight.org/gerrit/28022/

To revert the above change, I push the following patch.
https://git.opendaylight.org/gerrit/#/c/30509/
This needs to be reviewed by a committer of the autorelease project.

(In reply to Hideyuki Tai from comment #11)
> (In reply to Thanh Ha from comment #2)
> > This patch which temporarily disables VTN from autorelease should be
> > reverted when this bug is resolved:
> >
> > https://git.opendaylight.org/gerrit/28022/
>
> To revert the above change, I push the following patch.
> https://git.opendaylight.org/gerrit/#/c/30509/
> This needs to be reviewed by a committer of the autorelease project.

Thanks Hideyuki, it's been merged now. Hopefully we can get autorelease to build soon, I'm still waiting on a SNBI blocking patch [1] before we can see where we are at with autorelease.

[1] https://git.opendaylight.org/gerrit/30477/

I've confirmed that VTN build succeeds in autorelease job.

https://jenkins.opendaylight.org/releng/job/autorelease-daily-beryllium/313/

Confirmed that autorelease passed:

https://jenkins.opendaylight.org/releng/job/autorelease-daily-beryllium/lastSuccessfulBuild/

Link should have been:

https://jenkins.opendaylight.org/releng/job/autorelease-daily-beryllium/313/