Form Robert Varga Analysis:

https://lists.opendaylight.org/pipermail/release/2016-October/008570.html

Looking into this, the snapshots builds are fine, but there is something
very wrong with autorelease, as we have not published this artifact
since Be-SR4:

https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/centinel/centinelUI-bundle/

It also built in last successful Boron autorelease,
https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/47/,
it was installed:

[INFO] Installing
/w/workspace/autorelease-release-boron/centinel/ui/centinelUI-bundle/target/centinelUI-bundle-0.2.1-Boron-SR1.jar
to
/tmp/r/org/opendaylight/centinel/centinelUI-bundle/0.2.1-Boron-SR1/centinelUI-bundle-0.2.1-Boron-SR1.jar

the autorelease seems to have been deployed to the staging repo:

[INFO] Staging remotely locally deployed repository...
[INFO] + Using server credentials "opendaylight.staging" from Maven
settings.
[INFO] * Connected to Nexus at https://nexus.opendaylight.org:443/, is
version 2.14.0-01 and edition "Professional"
[INFO] * Created staging repository with ID "autorelease-1555".
[INFO] * Uploading locally staged artifacts to profile autorelease
[INFO] Starting upload transfer ID
"29582b61-0d1a-4fd0-8ade-46db7cc8b4ea" (using protocol "whole-zfile")
[INFO] Uploading total of 4937981080 bytes (in 11967 files) as 11967
segments (11967 payloads) over 6 tracks.
[INFO] Upload finished in 145 seconds.
[INFO] * Upload of locally staged artifacts finished.
[INFO] * Closing staging repository with ID "autorelease-1555".

Waiting for operation to complete..........

[INFO] Remote staging finished with success.

but it does not appear to be present in that staging repo:

https://nexus.opendaylight.org/content/repositories/autorelease-1555/org/opendaylight/centinel/

This does not look good and indicates we have not correctly released
Boron, either.