On Thu, Jun 21, 2018 at 7:33 PM, Faseela K <faseela.k@...> wrote:

Tomas was also indicating the same issue.
I don't have much clue about this -view section.
Tomas was asking to move this section to releng-views, but Anil told the current approach looks good enough.

@Anil : Any pointers on this issue? Should we move back the -view section back to releng-view?

Hello all,

Initially, ./builder/jjb/releng-views.yaml was common place holder for manging project specific views on Jenkins through

code because JJB versions earlier to 2.0.10 did not allow referencing anchors defined in other files. 

yaml.composer.ComposerError: found undefined alias 'releng_view_common' 

 in "~/git/builder-test-3/jjb/serviceutils/serviceutils.yaml", line 51, column 9

However, If you are seeing error similar to the above, please make sure you updated JJB to the latest 2.0.10  

this pulls in the change which supports referencing anchors across files [1.].

We want the views relevent to projects to by moved into the project yaml files.

Also add `retain_anchors=True` in Jenkins configuration (jenkins.ini). 

[1.] https://review.openstack.org/#/c/571197  

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 ?

On 6/21/18 7:45 AM, Thanh Ha wrote:
> On Thu, Jun 21, 2018 at 7:34 AM Anil Belur <abelur@... <mailto:abelur@...>> wrote:
>
>     On Thu, Jun 21, 2018 at 7:33 PM, Faseela K <faseela.k@... <mailto:faseela.k@...>> wrote:
>
>         Tomas was also indicating the same issue.
>         I don't have much clue about this -view section.
>         Tomas was asking to move this section to releng-views, but Anil told the current approach looks good enough.
>
>         @Anil : Any pointers on this issue? Should we move back the -view section back to releng-view?
>
>
>     Hello all,
>
>     Initially, ./builder/jjb/releng-views.yaml was common place holder for manging project specific views on Jenkins through
>     code because JJB versions earlier to 2.0.10 did not allow referencing anchors defined in other files.
>
>     yaml.composer.ComposerError: found undefined alias 'releng_view_common'
>       in "~/git/builder-test-3/jjb/serviceutils/serviceutils.yaml", line 51, column 9
>
>     However, If you are seeing error similar to the above, please make sure you updated JJB to the latest 2.0.10
>     this pulls in the change which supports referencing anchors across files [1.].
>
>     We want the views relevent to projects to by moved into the project yaml files.
>
>     Also add `retain_anchors=True` in Jenkins configuration (jenkins.ini).
>
>     [1.] https://review.openstack.org/#/c/571197
>
>
> 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.

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.

On 21/06/18 18:28, Thanh Ha wrote:
>
> 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:
>
>     https://git.opendaylight.org/gerrit/73321

This will work for the time being :)

Thanks a bunch,
Robert

_______________________________________________
integration-dev mailing list
integration-dev@...
https://lists.opendaylight.org/mailman/listinfo/integration-dev