manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shinichiro Abe (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1259) Use Travis CI
Date Tue, 24 Nov 2015 14:25:11 GMT


Shinichiro Abe commented on CONNECTORS-1259:

The build trigger is different between Jenkins and Travis. Jenkins is poring new commits which
is scheduled. OTOH, Travis runs a build on the commits when developers commit.
We have a problem, mvn developers doesn't run ant test, ant developers doesn't run mvn test.
Travis will be able to verify commits just in time. Of course we have to avoid the automated
builds failure like many build emails in lucene/solr team.

> Use Travis CI
> -------------
>                 Key: CONNECTORS-1259
>                 URL:
>             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  (public)
after committing. And we can add the status badge to somewhere such as README.
> !!
> (1)
> (2)

This message was sent by Atlassian JIRA

View raw message