Re: [opendaylight-dev] serviceutils view in jjb messing up my jenkins-job pushing
Thanh Ha <thanh.ha@...>
On Thu, Jun 21, 2018 at 11:27 AM Robert Varga <nite@...> wrote:
On 21/06/18 17:17, Thanh Ha wrote:
I tracked this down. It was caused by the upgrade to global-jjb v0.21.0 patch:
After inspecting the commit log of global-jjb for versions between v0.19.2 to v0.21.0 and release notes:
The patch 10394 changes the "default" Maven version from mvn33 to mvn35 in the global-jjb template and in releng/builder we were not overriding the mvn-version for the javadoc job. Normally we override via the job-group here:
but the javadoc jobs are not in that list so was accepting the default value coming from upstream global-jjb. This is why the javadoc jobs did not switch to mvn35 when we migrated all the other jobs.
With that said, if mvn35 is causing issues for mdsal, we can explicitly set the version back to mvn33 for the javadoc job with this patch:
In hindsight this is definitely something we missed in evaluating impact of the global-jjb upgrade as missed the fact that javadoc job mvn-version setting was pulling in the default value rather than the value explicitly set by the ODL job group. This is because not all projects have javadocs to publish so it was not included in the job-group. Moving forward one solution is to ensure that every project that specifies a "javadoc" job in their JJB YAML that they explicitly set the mvn-version setting to ensure we do not get surprises like this again in the future.