[
https://issues.apache.org/jira/browse/STREAMS-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150770#comment-16150770
]
Steve Blackmon edited comment on STREAMS-394 at 9/1/17 4:01 PM:
----------------------------------------------------------------
There are two benefits of using travis at all:
1) Easy to run against pull request branches
2) Nice to see the build results attached to the pull requests in github
However, there have been major problems using travis with streams:
1) It doesn't like builds that run as long as our builds run
2) It doesn't like builds as verbose as our builds are
3) Unlike jenkins, it can't access encrypted secrets stored outside the source
tree (such as SNS API credentials)
4) Unlike jenkins, it doesn't have a working docker environment (needed for
streams-persist integration testing)
It seems logical to me to turn off travis and invest in setting up jenkins to
build pull request branches.
I suggest we change this ticket to 'discontinue use of travis altogether' and
create a series of tickets to improve our jenkins setup until we can run all
tests on every pull request and get an indication of the result on the github
PR.
was (Author: steveblackmon):
There are two benefits of using travis at all:
1) Easy to run against pull request branches
2) Nice to see the build results attached to the pull requests in github
However, there have been major problems using travis with streams:
1) It doesn't like builds that run as long as our builds run
2) It doesn't like builds as verbose as our builds are
3) Unlike jenkins, it can't access encrypted secrets stored outside the source
tree (such as SNS API credentials)
4) Unlike jenkins, it doesn't have a working docker environment (needed for
streams-persist integration testing)
It seems logical to me to turn off travis and invest in setting up jenkins to
build pull request branches.
> Ensure that at least a subset of tests are able to run in travis CI
> -------------------------------------------------------------------
>
> Key: STREAMS-394
> URL: https://issues.apache.org/jira/browse/STREAMS-394
> Project: Streams
> Issue Type: Improvement
> Reporter: Steve Blackmon
> Assignee: Steve Blackmon
>
> Test execution in travis has been disabled because travis was unable to
> complete the full test suite. Determine what subset of tests travis can
> handle (might be all once STREAMS-392 merges) and enable test execution in
> .travis.yml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
