[
https://issues.apache.org/jira/browse/JENA-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15558164#comment-15558164
]
Andy Seaborne commented on JENA-1241:
-------------------------------------
We already have a Jenkins job that runs on each git commit.
What does this give us? I not againt it but I want to understand why given we
have very similar functionality elsewhere.
Doesn't it mean that when someone clones Jena and adds it to Travis-CI
> Enable Travis-CI for Jena
> -------------------------
>
> Key: JENA-1241
> URL: https://issues.apache.org/jira/browse/JENA-1241
> Project: Apache Jena
> Issue Type: Improvement
> Components: Build
> Affects Versions: Jena 3.1.0, Fuseki 2.4.0
> Reporter: A. Soroka
> Assignee: A. Soroka
> Priority: Minor
> Labels: CI
> Fix For: Jena 3.1.1, Fuseki 2.4.1
>
>
> Travis-CI is a nice and very well integrated CI service that offers free
> support to projects with few demands. To take advantage of it we just need to
> include a .travis.yml file in our codebase to configure our use of the
> service and activate the Github apache/jena repository.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
