[
https://issues.apache.org/jira/browse/CONNECTORS-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024546#comment-15024546
]
Shinichiro Abe commented on CONNECTORS-1259:
--------------------------------------------
Hi Karl,
FYI: https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
It seems INFRA team supports "30 concurrent builds", so it does not mean only
mcf-build-machine guarantees to build. There have possibilities to be
overloaded on the build machine. Should I have to config a param -DskipITs=true
or make all tests be disabled?
> 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)
