On 21/06/18 17:17, Thanh Ha wrote:

On Thu, Jun 21, 2018 at 11:08 AM Robert Varga <nite@...
<mailto:nite@...>> wrote:

On 21/06/18 16:50, Jamo Luhrsen wrote:
>> Seems like a breaking change for ODL's JJB users. We should document
>> this, update the example jenkins.ini.example in releng/builder and
>> notify the community when a change like this is requires users to
>> modify their environment.
>
> I think this is happening every 1-2 months lately.

Could this also explain why verify-javadoc jobs are suddenly using mvn35
instead of mvn33 ?


Hi Robert,

That was caused by this patch
https://git.opendaylight.org/gerrit/71087 which was merged 9 weeks ago.
Which was a result of this
Jira https://jira.opendaylight.org/browse/RELENG-97 when we were having
off-by-1 artifact issues with the Nitrogen stream back when we were
trying to get Nitrogen-SR3 out the door.

There was a decision on the mailing
list https://lists.opendaylight.org/pipermail/release/2018-April/014799.html
to migrate to Maven 3.5.3 moving forward so that we would (hopefully)
stop hitting that off by 1 artifact bug in maven versions < 3.5.2.
Initially we only rolled it out to merge jobs to get over the
Nitrogen-SR3 blocker but eventually rolled it out to the remaining jobs.

Thanks for the clarification, but it was rolled out between

https://jenkins.opendaylight.org/releng/job/mdsal-maven-javadoc-verify-fluorine/1123/
https://jenkins.opendaylight.org/releng/job/mdsal-maven-javadoc-verify-fluorine/1125/

i.e. on June 19, with no mention of this happening. mdsal now cannot
successfully verify and after spending a day on the issue I am no closer
to seeing a way to resolve it.

Regards,
Robert