[
https://issues.apache.org/jira/browse/CONNECTORS-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024559#comment-15024559
]
Karl Wright commented on CONNECTORS-1259:
-----------------------------------------
Hi Abe-san,
I don't know what the right approach is, except that MCF's tests are often
timed and therefore cannot succeed when the machine they are run on is under
significant load. If the automated builds fail once in a while, that is OK,
but if they fail all the time then it is not worth having the tests run there.
> Use Travis CI
> -------------
>
> Key: CONNECTORS-1259
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1259
> Project: ManifoldCF
> Issue Type: Test
> Components: Tests
> Affects Versions: ManifoldCF 2.2
> Reporter: Shinichiro Abe
> Assignee: Shinichiro Abe
> Priority: Minor
> Attachments: CONNECTORS-1259.patch, myrepo-ci-result.png
>
>
> Jenkins builds supports mcf-ant and mcf-mvn today. mcf-ant includes tests but
> mcf-mvn does not include test:
> {noformat}
> mvn -DskipTests=false -DskipITs=true clean -DskipTests -DskipITs install
> {noformat}
> It would be nice we could run "mvn install" rather than that.
> Some Apache projects are using travis ci via Github(1), just putting
> .travis.yml to project root directory.
> And these tests are not limited timeout as to a build(2).
> I tried to test mcf trunk using travis.yml on my repo, then tests work well.
> Please see attached image.
> We can watch the testing result at https://travis-ci.org/apache/manifoldcf
> (public) after committing. And we can add the status badge to somewhere such
> as README.
> !https://travis-ci.org/sabe1/manifoldcf.svg?branch=trunk!
> (1)
> https://travis-ci.org/apache/jackrabbit-oak
> https://travis-ci.org/apache/storm
> (2)
> https://docs.travis-ci.com/user/customizing-the-build/#Build-Timeouts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
