[
https://issues.apache.org/jira/browse/OAK-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356744#comment-15356744
]
Davide Giannella commented on OAK-4475:
---------------------------------------
I don't like these kind of things in the code but I can't see any other way
around it. Another solution would be to backport the Fixture into the branches
as well but as an "empty"/"no-op" one. Something we have to create if we want
to go in such direction.
Nevertheless, there's no direct hard-binding between the fixtures in
{{FixturesHelper}} and the actual fixtures. We should fix it making it a unique
class so that the helper relates to the actual fixtures we have in the project.
So, IIRC, it should be safe enough to create the fixture in {{FixturesHelper}};
but I fear it will be even more misleading and error to unforeseen conditions.
I gave a look as well in the matrix configuration on jenkins to see whether it
would have been possible to consider the current branch in the matrix filter
but didn't find any real help around the web.
> CI failing on branches due to unknown fixture SEGMENT_TAR
> ---------------------------------------------------------
>
> Key: OAK-4475
> URL: https://issues.apache.org/jira/browse/OAK-4475
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Michael Dürig
> Assignee: Chetan Mehrotra
> Labels: CI, build, jenkins
> Fix For: 1.6
>
> Attachments: OAK-4475-v1.patch
>
>
> These failures are caused by adding the SEGMENT_TAR fixture to the matrix.
> That one doesn't exit in the branches thus the {{IllegalArgumentException}}
> "No enum constant".
> See discussion http://markmail.org/message/oaptnvco5y2a4rjk
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
