[ 
https://issues.apache.org/jira/browse/JENA-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15558195#comment-15558195
 ] 

A. Soroka commented on JENA-1241:
---------------------------------

1. I think you are asking about getting duplicate notifications for clones of 
the Github repo? No, that won't happen. Travis_CI integrates tightly with 
Github and thereby knows enough to only send notes to owners of repos. So for 
example, if I have a PR against Jena from a branch in my repo, and that branch 
fails to build, only I will be notified by email. But I _will_ be notified, 
which leads me to the next point:

2. What we get is per-branch notification directly (and only) to people 
involved with that branch. (But only if the people in question opt-in allow 
it.) So as I am working on my crazy weird branch of Jena in my own repo, I get 
good CI and notifications therefrom without affecting anyone else or annoying 
the whole project with notifications. I don't thin I can get that now from 
Jenkins, or if I can, I don't imagine non-committers can.

3. The IRC thing isn't very important. I find it really nice to get 
notifications for those things in IRC, and Jena's dev@ already sends a _lot_ of 
email per change (lots of duplicates, thanks to bouncing between Github and 
Jira), but I'm in no way committed to IRC stuff. I can take that out if there's 
an objection.

> 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)

Reply via email to