Mailing-List: contact dev-help@flume.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flume.apache.org
MIME-Version: 1.0
In-Reply-To: <CANzZpc79=RXfruDa+Mm4RAMHBdccDi2yr1aH2CuQofipvOoqpA@mail.gmail.com>
References: <CANzZpc5yVvm1vFPPgzSoPPwdTuY5yio0PW8t874i8M+WTzvw6g@mail.gmail.com>
 <CANzZpc7icLD1LA=pfDA1sy0xr4djjDPje-a2O0dRizKnO51_Mg@mail.gmail.com>
 <CANzZpc6Fykot5u=NuisNG5w7FTsY4xcgu-JN4UmhGnzyjzwRgw@mail.gmail.com>
 <CANzZpc5xhrRfS8nNCc0-wO-eAN5mEefM=QNH1pzUwKMiwe1cZg@mail.gmail.com> <CANzZpc79=RXfruDa+Mm4RAMHBdccDi2yr1aH2CuQofipvOoqpA@mail.gmail.com>
From: Lior Zeno <liorzino@gmail.com>
Date: Thu, 13 Oct 2016 19:06:14 +0300
Message-ID: <CAA6RhS-58EpH6pShjfSCDyiN-L3QX=vXjJpyr1CQzegkfe1XjA@mail.gmail.com>
Subject: Re: Enabling Travis-CI on Flume
To: dev@flume.apache.org
Content-Type: multipart/alternative; boundary=001a114b33102ce2f6053ec14b5e
archived-at: Thu, 13 Oct 2016 16:06:39 -0000

--001a114b33102ce2f6053ec14b5e
Content-Type: text/plain; charset=UTF-8

Jenkins can do PRs as well. If we can upgrade Jenkins to 2.0, we will be
able to define the build step via Jenkinsfile which becomes very similar to
Travis.
Is there any reason to prefer Travis over Jenkins in our case?

On Thu, Oct 13, 2016 at 7:01 PM, Balazs Donat Bessenyei <bessbd@cloudera.com
> wrote:

> Hi All,
>
> Having something that checks proposed patches (PR-s especially)
> automatically would help a lot with the development on Flume.
>
> I think, Travis-CI could be an easy solution and (afaik) we'd only have to
> ask infra to enable it for us.
>
> Please, let me know your thoughts.
>
> Thank you,
>
> Donat
>

--001a114b33102ce2f6053ec14b5e--