>From what I understood, it is to be used by other contributors using GitHub, >in their own repositories. Whereas Jena itsefl would continue using Jenkins.
----- Original Message ----- > From: Claude Warren <[email protected]> > To: [email protected] > Sent: Tuesday, 11 October 2016 7:17 PM > Subject: Re: [jira] [Commented] (JENA-1241) Enable Travis-CI for Jena > > Is this a move away from Jenkins then? > > Claude > > > On Tue, Oct 11, 2016 at 1:05 AM, A. Soroka (JIRA) <[email protected]> wrote: > >> >> [ https://issues.apache.org/jira/browse/JENA-1241?page= >> com.atlassian.jira.plugin.system.issuetabpanels:comment- >> tabpanel&focusedCommentId=15563956#comment-15563956 ] >> >> A. Soroka commented on JENA-1241: >> --------------------------------- >> >> Cool. Would you like me to check in with INFRA about this before we go >> ahead-- maybe see if they have a policy about this or are developing one? >> >> > 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) >> > > > > -- > I like: Like Like - The likeliest place on the web > <http://like-like.xenei.com> > LinkedIn: http://www.linkedin.com/in/claudewarren >
