[
https://issues.apache.org/jira/browse/AMBARI-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012116#comment-16012116
]
Hudson commented on AMBARI-21020:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7477 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7477/])
AMBARI-21020. Support external story locations in Log Search IT (oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e54252c829f674919d51d38c33689cce7a17e075])
* (edit) ambari-logsearch/ambari-logsearch-it/pom.xml
* (edit)
ambari-logsearch/ambari-logsearch-it/src/test/java/org/apache/ambari/logsearch/story/LogSearchBackendStories.java
* (add)
ambari-logsearch/ambari-logsearch-it/src/test/java/org/apache/ambari/logsearch/story/LogSearchStoryLocator.java
* (edit) ambari-logsearch/README.md
* (edit)
ambari-logsearch/ambari-logsearch-it/src/test/java/org/apache/ambari/logsearch/story/LogSearchUIStories.java
> Support external story locations in Log Search IT framework
> -----------------------------------------------------------
>
> Key: AMBARI-21020
> URL: https://issues.apache.org/jira/browse/AMBARI-21020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.5.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 3.0.0
>
>
> Currently, logsearch it framework load story files (JBhave) from the
> classpath, it would be useful to load story files externally, then we should
> not manage story files inside the source code. (helps to write business
> specific tests without code change)
> To achive this, add 2 new properties to the build:
> {{backend.stories.location}} and {{ui.stories.location properties}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
