Travis-CI builds queuing up

[Robert Metzger]

Hi guys,

the build queue on travis is getting very very long. It seems that it takes
4 days now until commits to master are build. The nightly builds from the
website and the maven snapshots are also delayed by that.
Right now,  there are 33 pull request builds scheduled (
https://travis-ci.org/apache/flink/pull_requests), and 8 builds on master:
https://travis-ci.org/apache/flink/builds.

The problem is that travis accounts are per github user. In our case, the
user is "apache", so all ASF projects that have travis enabled share 5
concurrent builders.

I would actually like to continue using Travis.

The easiest option is probably asking travis if they can give the "apache"
user more build capacity.

If thats not possible, we have to look into other options.


I'm going to ask Travis if they can do anything about it.

Robert

[Márton Balassi]

I also like the travis infrastucture. Thanks for bringing this up and
reaching out to the travis guys.

On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <[hidden email]> wrote:

> Hi guys,
>
> the build queue on travis is getting very very long. It seems that it takes
> 4 days now until commits to master are build. The nightly builds from the
> website and the maven snapshots are also delayed by that.
> Right now,  there are 33 pull request builds scheduled (
> https://travis-ci.org/apache/flink/pull_requests), and 8 builds on master:
> https://travis-ci.org/apache/flink/builds.
>
> The problem is that travis accounts are per github user. In our case, the
> user is "apache", so all ASF projects that have travis enabled share 5
> concurrent builders.
>
> I would actually like to continue using Travis.
>
> The easiest option is probably asking travis if they can give the "apache"
> user more build capacity.
>
> If thats not possible, we have to look into other options.
>
>
> I'm going to ask Travis if they can do anything about it.
>
> Robert
>

[mxm]

Hey!

I would also like to continue using Travis but the current situation is not
acceptable because we practically can't use Travis anymore for pull
requests or the current master. If it cannot be resolved then I think we
should move on.

The builds service team [1] at Apache offers Jenkins [2] for continuous
integration. I think it should be fairly simple to set up. We could still
use Travis in our forked repositories but have a reliable CI solution for
the master and pull requests.

Max

[1] https://builds.apache.org/
[2] http://jenkins-ci.org

On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <[hidden email]>
wrote:

> I also like the travis infrastucture. Thanks for bringing this up and
> reaching out to the travis guys.
>
> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <[hidden email]>
> wrote:
>
> > Hi guys,
> >
> > the build queue on travis is getting very very long. It seems that it
> takes
> > 4 days now until commits to master are build. The nightly builds from the
> > website and the maven snapshots are also delayed by that.
> > Right now,  there are 33 pull request builds scheduled (
> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds on
> master:
> > https://travis-ci.org/apache/flink/builds.
> >
> > The problem is that travis accounts are per github user. In our case, the
> > user is "apache", so all ASF projects that have travis enabled share 5
> > concurrent builders.
> >
> > I would actually like to continue using Travis.
> >
> > The easiest option is probably asking travis if they can give the
> "apache"
> > user more build capacity.
> >
> > If thats not possible, we have to look into other options.
> >
> >
> > I'm going to ask Travis if they can do anything about it.
> >
> > Robert
> >
>

[Henry Saputra]

If we could not get more capacity we could set up ASF Jenkins instead.
It is already used to power CI for many ASF projects like Hadoop so should
not be too shabby.

I have created ticket for Flink to setup ASF Jenkins but have not found
time to work on it.

- Henry

On Tuesday, March 24, 2015, Robert Metzger <[hidden email]> wrote:

> Hi guys,
>
> the build queue on travis is getting very very long. It seems that it takes
> 4 days now until commits to master are build. The nightly builds from the
> website and the maven snapshots are also delayed by that.
> Right now,  there are 33 pull request builds scheduled (
> https://travis-ci.org/apache/flink/pull_requests), and 8 builds on master:
> https://travis-ci.org/apache/flink/builds.
>
> The problem is that travis accounts are per github user. In our case, the
> user is "apache", so all ASF projects that have travis enabled share 5
> concurrent builders.
>
> I would actually like to continue using Travis.
>
> The easiest option is probably asking travis if they can give the "apache"
> user more build capacity.
>
> If thats not possible, we have to look into other options.
>
>
> I'm going to ask Travis if they can do anything about it.
>
> Robert
>

[Ufuk Celebi-2]

Let's see what Travis replies to Robert, but in general I agree with Max.

Travis helped a lot to discover certain race conditions in the last weeks... I would like to not ditch it completely as Max suggested.

On 24 Mar 2015, at 16:03, Maximilian Michels <[hidden email]> wrote:

> I would also like to continue using Travis but the current situation is not
> acceptable because we practically can't use Travis anymore for pull
> requests or the current master. If it cannot be resolved then I think we
> should move on.
> The builds service team [1] at Apache offers Jenkins [2] for continuous
> integration. I think it should be fairly simple to set up. We could still
> use Travis in our forked repositories but have a reliable CI solution for
> the master and pull requests.

[Henry Saputra]

That's good idea.

Should be good to have mix of stable with Apache Jenkins for master
and PRs, and Travis for individual forks.

- Henry

On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <[hidden email]> wrote:

> Hey!
>
> I would also like to continue using Travis but the current situation is not
> acceptable because we practically can't use Travis anymore for pull
> requests or the current master. If it cannot be resolved then I think we
> should move on.
>
> The builds service team [1] at Apache offers Jenkins [2] for continuous
> integration. I think it should be fairly simple to set up. We could still
> use Travis in our forked repositories but have a reliable CI solution for
> the master and pull requests.
>
> Max
>
> [1] https://builds.apache.org/
> [2] http://jenkins-ci.org
>
> On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <[hidden email]>
> wrote:
>
>> I also like the travis infrastucture. Thanks for bringing this up and
>> reaching out to the travis guys.
>>
>> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <[hidden email]>
>> wrote:
>>
>> > Hi guys,
>> >
>> > the build queue on travis is getting very very long. It seems that it
>> takes
>> > 4 days now until commits to master are build. The nightly builds from the
>> > website and the maven snapshots are also delayed by that.
>> > Right now,  there are 33 pull request builds scheduled (
>> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds on
>> master:
>> > https://travis-ci.org/apache/flink/builds.
>> >
>> > The problem is that travis accounts are per github user. In our case, the
>> > user is "apache", so all ASF projects that have travis enabled share 5
>> > concurrent builders.
>> >
>> > I would actually like to continue using Travis.
>> >
>> > The easiest option is probably asking travis if they can give the
>> "apache"
>> > user more build capacity.
>> >
>> > If thats not possible, we have to look into other options.
>> >
>> >
>> > I'm going to ask Travis if they can do anything about it.
>> >
>> > Robert
>> >
>>

[Robert Metzger]

Travis replied me with very good news: Somebody from INFRA was asking the
same question around the same time as I did and Travis is working on adding
more build capacity for the "apache" github organization.
I hope we'll soon have quicker builds again.

On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <[hidden email]>
wrote:

> That's good idea.
>
> Should be good to have mix of stable with Apache Jenkins for master
> and PRs, and Travis for individual forks.
>
> - Henry
>
> On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <[hidden email]>
> wrote:
> > Hey!
> >
> > I would also like to continue using Travis but the current situation is
> not
> > acceptable because we practically can't use Travis anymore for pull
> > requests or the current master. If it cannot be resolved then I think we
> > should move on.
> >
> > The builds service team [1] at Apache offers Jenkins [2] for continuous
> > integration. I think it should be fairly simple to set up. We could still
> > use Travis in our forked repositories but have a reliable CI solution for
> > the master and pull requests.
> >
> > Max
> >
> > [1] https://builds.apache.org/
> > [2] http://jenkins-ci.org
> >
> > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> [hidden email]>
> > wrote:
> >
> >> I also like the travis infrastucture. Thanks for bringing this up and
> >> reaching out to the travis guys.
> >>
> >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <[hidden email]>
> >> wrote:
> >>
> >> > Hi guys,
> >> >
> >> > the build queue on travis is getting very very long. It seems that it
> >> takes
> >> > 4 days now until commits to master are build. The nightly builds from
> the
> >> > website and the maven snapshots are also delayed by that.
> >> > Right now,  there are 33 pull request builds scheduled (
> >> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds on
> >> master:
> >> > https://travis-ci.org/apache/flink/builds.
> >> >
> >> > The problem is that travis accounts are per github user. In our case,
> the
> >> > user is "apache", so all ASF projects that have travis enabled share 5
> >> > concurrent builders.
> >> >
> >> > I would actually like to continue using Travis.
> >> >
> >> > The easiest option is probably asking travis if they can give the
> >> "apache"
> >> > user more build capacity.
> >> >
> >> > If thats not possible, we have to look into other options.
> >> >
> >> >
> >> > I'm going to ask Travis if they can do anything about it.
> >> >
> >> > Robert
> >> >
> >>
>

[Fabian Hueske-2]

Great!
Thanks Robert for sharing the good news :-)

2015-03-26 9:08 GMT+01:00 Robert Metzger <[hidden email]>:

> Travis replied me with very good news: Somebody from INFRA was asking the
> same question around the same time as I did and Travis is working on adding
> more build capacity for the "apache" github organization.
> I hope we'll soon have quicker builds again.
>
> On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <[hidden email]>
> wrote:
>
> > That's good idea.
> >
> > Should be good to have mix of stable with Apache Jenkins for master
> > and PRs, and Travis for individual forks.
> >
> > - Henry
> >
> > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <[hidden email]>
> > wrote:
> > > Hey!
> > >
> > > I would also like to continue using Travis but the current situation is
> > not
> > > acceptable because we practically can't use Travis anymore for pull
> > > requests or the current master. If it cannot be resolved then I think
> we
> > > should move on.
> > >
> > > The builds service team [1] at Apache offers Jenkins [2] for continuous
> > > integration. I think it should be fairly simple to set up. We could
> still
> > > use Travis in our forked repositories but have a reliable CI solution
> for
> > > the master and pull requests.
> > >
> > > Max
> > >
> > > [1] https://builds.apache.org/
> > > [2] http://jenkins-ci.org
> > >
> > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> > [hidden email]>
> > > wrote:
> > >
> > >> I also like the travis infrastucture. Thanks for bringing this up and
> > >> reaching out to the travis guys.
> > >>
> > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <[hidden email]>
> > >> wrote:
> > >>
> > >> > Hi guys,
> > >> >
> > >> > the build queue on travis is getting very very long. It seems that
> it
> > >> takes
> > >> > 4 days now until commits to master are build. The nightly builds
> from
> > the
> > >> > website and the maven snapshots are also delayed by that.
> > >> > Right now,  there are 33 pull request builds scheduled (
> > >> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds on
> > >> master:
> > >> > https://travis-ci.org/apache/flink/builds.
> > >> >
> > >> > The problem is that travis accounts are per github user. In our
> case,
> > the
> > >> > user is "apache", so all ASF projects that have travis enabled
> share 5
> > >> > concurrent builders.
> > >> >
> > >> > I would actually like to continue using Travis.
> > >> >
> > >> > The easiest option is probably asking travis if they can give the
> > >> "apache"
> > >> > user more build capacity.
> > >> >
> > >> > If thats not possible, we have to look into other options.
> > >> >
> > >> >
> > >> > I'm going to ask Travis if they can do anything about it.
> > >> >
> > >> > Robert
> > >> >
> > >>
> >
>

[mxm]

That's nice to hear. They didn't specify any time frame?

On Thu, Mar 26, 2015 at 9:25 AM, Fabian Hueske <[hidden email]> wrote:

> Great!
> Thanks Robert for sharing the good news :-)
>
> 2015-03-26 9:08 GMT+01:00 Robert Metzger <[hidden email]>:
>
> > Travis replied me with very good news: Somebody from INFRA was asking the
> > same question around the same time as I did and Travis is working on
> adding
> > more build capacity for the "apache" github organization.
> > I hope we'll soon have quicker builds again.
> >
> > On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <[hidden email]>
> > wrote:
> >
> > > That's good idea.
> > >
> > > Should be good to have mix of stable with Apache Jenkins for master
> > > and PRs, and Travis for individual forks.
> > >
> > > - Henry
> > >
> > > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <[hidden email]>
> > > wrote:
> > > > Hey!
> > > >
> > > > I would also like to continue using Travis but the current situation
> is
> > > not
> > > > acceptable because we practically can't use Travis anymore for pull
> > > > requests or the current master. If it cannot be resolved then I think
> > we
> > > > should move on.
> > > >
> > > > The builds service team [1] at Apache offers Jenkins [2] for
> continuous
> > > > integration. I think it should be fairly simple to set up. We could
> > still
> > > > use Travis in our forked repositories but have a reliable CI solution
> > for
> > > > the master and pull requests.
> > > >
> > > > Max
> > > >
> > > > [1] https://builds.apache.org/
> > > > [2] http://jenkins-ci.org
> > > >
> > > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> > > [hidden email]>
> > > > wrote:
> > > >
> > > >> I also like the travis infrastucture. Thanks for bringing this up
> and
> > > >> reaching out to the travis guys.
> > > >>
> > > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <
> [hidden email]>
> > > >> wrote:
> > > >>
> > > >> > Hi guys,
> > > >> >
> > > >> > the build queue on travis is getting very very long. It seems that
> > it
> > > >> takes
> > > >> > 4 days now until commits to master are build. The nightly builds
> > from
> > > the
> > > >> > website and the maven snapshots are also delayed by that.
> > > >> > Right now,  there are 33 pull request builds scheduled (
> > > >> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds
> on
> > > >> master:
> > > >> > https://travis-ci.org/apache/flink/builds.
> > > >> >
> > > >> > The problem is that travis accounts are per github user. In our
> > case,
> > > the
> > > >> > user is "apache", so all ASF projects that have travis enabled
> > share 5
> > > >> > concurrent builders.
> > > >> >
> > > >> > I would actually like to continue using Travis.
> > > >> >
> > > >> > The easiest option is probably asking travis if they can give the
> > > >> "apache"
> > > >> > user more build capacity.
> > > >> >
> > > >> > If thats not possible, we have to look into other options.
> > > >> >
> > > >> >
> > > >> > I'm going to ask Travis if they can do anything about it.
> > > >> >
> > > >> > Robert
> > > >> >
> > > >>
> > >
> >
>

[Robert Metzger]

No, but we can ask David Nalley from Infra, he is talking to them.

On Thu, Mar 26, 2015 at 11:13 AM, Maximilian Michels <[hidden email]> wrote:

> That's nice to hear. They didn't specify any time frame?
>
> On Thu, Mar 26, 2015 at 9:25 AM, Fabian Hueske <[hidden email]> wrote:
>
> > Great!
> > Thanks Robert for sharing the good news :-)
> >
> > 2015-03-26 9:08 GMT+01:00 Robert Metzger <[hidden email]>:
> >
> > > Travis replied me with very good news: Somebody from INFRA was asking
> the
> > > same question around the same time as I did and Travis is working on
> > adding
> > > more build capacity for the "apache" github organization.
> > > I hope we'll soon have quicker builds again.
> > >
> > > On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <
> [hidden email]>
> > > wrote:
> > >
> > > > That's good idea.
> > > >
> > > > Should be good to have mix of stable with Apache Jenkins for master
> > > > and PRs, and Travis for individual forks.
> > > >
> > > > - Henry
> > > >
> > > > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <[hidden email]>
> > > > wrote:
> > > > > Hey!
> > > > >
> > > > > I would also like to continue using Travis but the current
> situation
> > is
> > > > not
> > > > > acceptable because we practically can't use Travis anymore for pull
> > > > > requests or the current master. If it cannot be resolved then I
> think
> > > we
> > > > > should move on.
> > > > >
> > > > > The builds service team [1] at Apache offers Jenkins [2] for
> > continuous
> > > > > integration. I think it should be fairly simple to set up. We could
> > > still
> > > > > use Travis in our forked repositories but have a reliable CI
> solution
> > > for
> > > > > the master and pull requests.
> > > > >
> > > > > Max
> > > > >
> > > > > [1] https://builds.apache.org/
> > > > > [2] http://jenkins-ci.org
> > > > >
> > > > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> > > > [hidden email]>
> > > > > wrote:
> > > > >
> > > > >> I also like the travis infrastucture. Thanks for bringing this up
> > and
> > > > >> reaching out to the travis guys.
> > > > >>
> > > > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <
> > [hidden email]>
> > > > >> wrote:
> > > > >>
> > > > >> > Hi guys,
> > > > >> >
> > > > >> > the build queue on travis is getting very very long. It seems
> that
> > > it
> > > > >> takes
> > > > >> > 4 days now until commits to master are build. The nightly builds
> > > from
> > > > the
> > > > >> > website and the maven snapshots are also delayed by that.
> > > > >> > Right now,  there are 33 pull request builds scheduled (
> > > > >> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds
> > on
> > > > >> master:
> > > > >> > https://travis-ci.org/apache/flink/builds.
> > > > >> >
> > > > >> > The problem is that travis accounts are per github user. In our
> > > case,
> > > > the
> > > > >> > user is "apache", so all ASF projects that have travis enabled
> > > share 5
> > > > >> > concurrent builders.
> > > > >> >
> > > > >> > I would actually like to continue using Travis.
> > > > >> >
> > > > >> > The easiest option is probably asking travis if they can give
> the
> > > > >> "apache"
> > > > >> > user more build capacity.
> > > > >> >
> > > > >> > If thats not possible, we have to look into other options.
> > > > >> >
> > > > >> >
> > > > >> > I'm going to ask Travis if they can do anything about it.
> > > > >> >
> > > > >> > Robert
> > > > >> >
> > > > >>
> > > >
> > >
> >
>

[mxm]

Yes, please. Would be interesting to know approximately when they implement
to extend the capacity for Apache repositories and how large it is going to
be.

On Thu, Mar 26, 2015 at 11:14 AM, Robert Metzger <[hidden email]>
wrote:

> No, but we can ask David Nalley from Infra, he is talking to them.
>
> On Thu, Mar 26, 2015 at 11:13 AM, Maximilian Michels <[hidden email]>
> wrote:
>
> > That's nice to hear. They didn't specify any time frame?
> >
> > On Thu, Mar 26, 2015 at 9:25 AM, Fabian Hueske <[hidden email]>
> wrote:
> >
> > > Great!
> > > Thanks Robert for sharing the good news :-)
> > >
> > > 2015-03-26 9:08 GMT+01:00 Robert Metzger <[hidden email]>:
> > >
> > > > Travis replied me with very good news: Somebody from INFRA was asking
> > the
> > > > same question around the same time as I did and Travis is working on
> > > adding
> > > > more build capacity for the "apache" github organization.
> > > > I hope we'll soon have quicker builds again.
> > > >
> > > > On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <
> > [hidden email]>
> > > > wrote:
> > > >
> > > > > That's good idea.
> > > > >
> > > > > Should be good to have mix of stable with Apache Jenkins for master
> > > > > and PRs, and Travis for individual forks.
> > > > >
> > > > > - Henry
> > > > >
> > > > > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <
> [hidden email]>
> > > > > wrote:
> > > > > > Hey!
> > > > > >
> > > > > > I would also like to continue using Travis but the current
> > situation
> > > is
> > > > > not
> > > > > > acceptable because we practically can't use Travis anymore for
> pull
> > > > > > requests or the current master. If it cannot be resolved then I
> > think
> > > > we
> > > > > > should move on.
> > > > > >
> > > > > > The builds service team [1] at Apache offers Jenkins [2] for
> > > continuous
> > > > > > integration. I think it should be fairly simple to set up. We
> could
> > > > still
> > > > > > use Travis in our forked repositories but have a reliable CI
> > solution
> > > > for
> > > > > > the master and pull requests.
> > > > > >
> > > > > > Max
> > > > > >
> > > > > > [1] https://builds.apache.org/
> > > > > > [2] http://jenkins-ci.org
> > > > > >
> > > > > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> > > > > [hidden email]>
> > > > > > wrote:
> > > > > >
> > > > > >> I also like the travis infrastucture. Thanks for bringing this
> up
> > > and
> > > > > >> reaching out to the travis guys.
> > > > > >>
> > > > > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <
> > > [hidden email]>
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hi guys,
> > > > > >> >
> > > > > >> > the build queue on travis is getting very very long. It seems
> > that
> > > > it
> > > > > >> takes
> > > > > >> > 4 days now until commits to master are build. The nightly
> builds
> > > > from
> > > > > the
> > > > > >> > website and the maven snapshots are also delayed by that.
> > > > > >> > Right now,  there are 33 pull request builds scheduled (
> > > > > >> > https://travis-ci.org/apache/flink/pull_requests), and 8
> builds
> > > on
> > > > > >> master:
> > > > > >> > https://travis-ci.org/apache/flink/builds.
> > > > > >> >
> > > > > >> > The problem is that travis accounts are per github user. In
> our
> > > > case,
> > > > > the
> > > > > >> > user is "apache", so all ASF projects that have travis enabled
> > > > share 5
> > > > > >> > concurrent builders.
> > > > > >> >
> > > > > >> > I would actually like to continue using Travis.
> > > > > >> >
> > > > > >> > The easiest option is probably asking travis if they can give
> > the
> > > > > >> "apache"
> > > > > >> > user more build capacity.
> > > > > >> >
> > > > > >> > If thats not possible, we have to look into other options.
> > > > > >> >
> > > > > >> >
> > > > > >> > I'm going to ask Travis if they can do anything about it.
> > > > > >> >
> > > > > >> > Robert
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
>

[Henry Saputra]

Awesome news!

On Thursday, March 26, 2015, Robert Metzger <[hidden email]> wrote:

> Travis replied me with very good news: Somebody from INFRA was asking the
> same question around the same time as I did and Travis is working on adding
> more build capacity for the "apache" github organization.
> I hope we'll soon have quicker builds again.
>
> On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <[hidden email]
> <javascript:;>>
> wrote:
>
> > That's good idea.
> >
> > Should be good to have mix of stable with Apache Jenkins for master
> > and PRs, and Travis for individual forks.
> >
> > - Henry
> >
> > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <[hidden email]
> <javascript:;>>
> > wrote:
> > > Hey!
> > >
> > > I would also like to continue using Travis but the current situation is
> > not
> > > acceptable because we practically can't use Travis anymore for pull
> > > requests or the current master. If it cannot be resolved then I think
> we
> > > should move on.
> > >
> > > The builds service team [1] at Apache offers Jenkins [2] for continuous
> > > integration. I think it should be fairly simple to set up. We could
> still
> > > use Travis in our forked repositories but have a reliable CI solution
> for
> > > the master and pull requests.
> > >
> > > Max
> > >
> > > [1] https://builds.apache.org/
> > > [2] http://jenkins-ci.org
> > >
> > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> > [hidden email] <javascript:;>>
> > > wrote:
> > >
> > >> I also like the travis infrastucture. Thanks for bringing this up and
> > >> reaching out to the travis guys.
> > >>
> > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <[hidden email]
> <javascript:;>>
> > >> wrote:
> > >>
> > >> > Hi guys,
> > >> >
> > >> > the build queue on travis is getting very very long. It seems that
> it
> > >> takes
> > >> > 4 days now until commits to master are build. The nightly builds
> from
> > the
> > >> > website and the maven snapshots are also delayed by that.
> > >> > Right now,  there are 33 pull request builds scheduled (
> > >> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds on
> > >> master:
> > >> > https://travis-ci.org/apache/flink/builds.
> > >> >
> > >> > The problem is that travis accounts are per github user. In our
> case,
> > the
> > >> > user is "apache", so all ASF projects that have travis enabled
> share 5
> > >> > concurrent builders.
> > >> >
> > >> > I would actually like to continue using Travis.
> > >> >
> > >> > The easiest option is probably asking travis if they can give the
> > >> "apache"
> > >> > user more build capacity.
> > >> >
> > >> > If thats not possible, we have to look into other options.
> > >> >
> > >> >
> > >> > I'm going to ask Travis if they can do anything about it.
> > >> >
> > >> > Robert
> > >> >
> > >>
> >
>

[Robert Metzger]

It seems that the issue is fixed. I've just pushed two times to a pull
request and it immediately started building both.
I think the "apache" user has much more parallel builds available now (we
don't have any builds queuing up anymore).

On Thu, Mar 26, 2015 at 4:06 PM, Henry Saputra <[hidden email]>
wrote:

> Awesome news!
>
> On Thursday, March 26, 2015, Robert Metzger <[hidden email]> wrote:
>
> > Travis replied me with very good news: Somebody from INFRA was asking the
> > same question around the same time as I did and Travis is working on
> adding
> > more build capacity for the "apache" github organization.
> > I hope we'll soon have quicker builds again.
> >
> > On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <[hidden email]
> > <javascript:;>>
> > wrote:
> >
> > > That's good idea.
> > >
> > > Should be good to have mix of stable with Apache Jenkins for master
> > > and PRs, and Travis for individual forks.
> > >
> > > - Henry
> > >
> > > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <[hidden email]
> > <javascript:;>>
> > > wrote:
> > > > Hey!
> > > >
> > > > I would also like to continue using Travis but the current situation
> is
> > > not
> > > > acceptable because we practically can't use Travis anymore for pull
> > > > requests or the current master. If it cannot be resolved then I think
> > we
> > > > should move on.
> > > >
> > > > The builds service team [1] at Apache offers Jenkins [2] for
> continuous
> > > > integration. I think it should be fairly simple to set up. We could
> > still
> > > > use Travis in our forked repositories but have a reliable CI solution
> > for
> > > > the master and pull requests.
> > > >
> > > > Max
> > > >
> > > > [1] https://builds.apache.org/
> > > > [2] http://jenkins-ci.org
> > > >
> > > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> > > [hidden email] <javascript:;>>
> > > > wrote:
> > > >
> > > >> I also like the travis infrastucture. Thanks for bringing this up
> and
> > > >> reaching out to the travis guys.
> > > >>
> > > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <
> [hidden email]
> > <javascript:;>>
> > > >> wrote:
> > > >>
> > > >> > Hi guys,
> > > >> >
> > > >> > the build queue on travis is getting very very long. It seems that
> > it
> > > >> takes
> > > >> > 4 days now until commits to master are build. The nightly builds
> > from
> > > the
> > > >> > website and the maven snapshots are also delayed by that.
> > > >> > Right now,  there are 33 pull request builds scheduled (
> > > >> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds
> on
> > > >> master:
> > > >> > https://travis-ci.org/apache/flink/builds.
> > > >> >
> > > >> > The problem is that travis accounts are per github user. In our
> > case,
> > > the
> > > >> > user is "apache", so all ASF projects that have travis enabled
> > share 5
> > > >> > concurrent builders.
> > > >> >
> > > >> > I would actually like to continue using Travis.
> > > >> >
> > > >> > The easiest option is probably asking travis if they can give the
> > > >> "apache"
> > > >> > user more build capacity.
> > > >> >
> > > >> > If thats not possible, we have to look into other options.
> > > >> >
> > > >> >
> > > >> > I'm going to ask Travis if they can do anything about it.
> > > >> >
> > > >> > Robert
> > > >> >
> > > >>
> > >
> >
>

[mxm]

Very nice. Thanks Robert!

On Mon, Mar 30, 2015 at 9:13 PM, Robert Metzger <[hidden email]> wrote:

> It seems that the issue is fixed. I've just pushed two times to a pull
> request and it immediately started building both.
> I think the "apache" user has much more parallel builds available now (we
> don't have any builds queuing up anymore).
>
> On Thu, Mar 26, 2015 at 4:06 PM, Henry Saputra <[hidden email]>
> wrote:
>
> > Awesome news!
> >
> > On Thursday, March 26, 2015, Robert Metzger <[hidden email]> wrote:
> >
> > > Travis replied me with very good news: Somebody from INFRA was asking
> the
> > > same question around the same time as I did and Travis is working on
> > adding
> > > more build capacity for the "apache" github organization.
> > > I hope we'll soon have quicker builds again.
> > >
> > > On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <
> [hidden email]
> > > <javascript:;>>
> > > wrote:
> > >
> > > > That's good idea.
> > > >
> > > > Should be good to have mix of stable with Apache Jenkins for master
> > > > and PRs, and Travis for individual forks.
> > > >
> > > > - Henry
> > > >
> > > > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <[hidden email]
> > > <javascript:;>>
> > > > wrote:
> > > > > Hey!
> > > > >
> > > > > I would also like to continue using Travis but the current
> situation
> > is
> > > > not
> > > > > acceptable because we practically can't use Travis anymore for pull
> > > > > requests or the current master. If it cannot be resolved then I
> think
> > > we
> > > > > should move on.
> > > > >
> > > > > The builds service team [1] at Apache offers Jenkins [2] for
> > continuous
> > > > > integration. I think it should be fairly simple to set up. We could
> > > still
> > > > > use Travis in our forked repositories but have a reliable CI
> solution
> > > for
> > > > > the master and pull requests.
> > > > >
> > > > > Max
> > > > >
> > > > > [1] https://builds.apache.org/
> > > > > [2] http://jenkins-ci.org
> > > > >
> > > > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> > > > [hidden email] <javascript:;>>
> > > > > wrote:
> > > > >
> > > > >> I also like the travis infrastucture. Thanks for bringing this up
> > and
> > > > >> reaching out to the travis guys.
> > > > >>
> > > > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <
> > [hidden email]
> > > <javascript:;>>
> > > > >> wrote:
> > > > >>
> > > > >> > Hi guys,
> > > > >> >
> > > > >> > the build queue on travis is getting very very long. It seems
> that
> > > it
> > > > >> takes
> > > > >> > 4 days now until commits to master are build. The nightly builds
> > > from
> > > > the
> > > > >> > website and the maven snapshots are also delayed by that.
> > > > >> > Right now,  there are 33 pull request builds scheduled (
> > > > >> > https://travis-ci.org/apache/flink/pull_requests), and 8 builds
> > on
> > > > >> master:
> > > > >> > https://travis-ci.org/apache/flink/builds.
> > > > >> >
> > > > >> > The problem is that travis accounts are per github user. In our
> > > case,
> > > > the
> > > > >> > user is "apache", so all ASF projects that have travis enabled
> > > share 5
> > > > >> > concurrent builders.
> > > > >> >
> > > > >> > I would actually like to continue using Travis.
> > > > >> >
> > > > >> > The easiest option is probably asking travis if they can give
> the
> > > > >> "apache"
> > > > >> > user more build capacity.
> > > > >> >
> > > > >> > If thats not possible, we have to look into other options.
> > > > >> >
> > > > >> >
> > > > >> > I'm going to ask Travis if they can do anything about it.
> > > > >> >
> > > > >> > Robert
> > > > >> >
> > > > >>
> > > >
> > >
> >
>

[Robert Metzger]

I just found out that the execution time limit for the container-based
infra (the one we're using) is 120 minutes ;)
So we have some room left to write more test ;) (But please don't overdo it
)

On Tue, Mar 31, 2015 at 11:32 AM, Maximilian Michels <[hidden email]> wrote:

> Very nice. Thanks Robert!
>
> On Mon, Mar 30, 2015 at 9:13 PM, Robert Metzger <[hidden email]>
> wrote:
>
> > It seems that the issue is fixed. I've just pushed two times to a pull
> > request and it immediately started building both.
> > I think the "apache" user has much more parallel builds available now (we
> > don't have any builds queuing up anymore).
> >
> > On Thu, Mar 26, 2015 at 4:06 PM, Henry Saputra <[hidden email]>
> > wrote:
> >
> > > Awesome news!
> > >
> > > On Thursday, March 26, 2015, Robert Metzger <[hidden email]>
> wrote:
> > >
> > > > Travis replied me with very good news: Somebody from INFRA was asking
> > the
> > > > same question around the same time as I did and Travis is working on
> > > adding
> > > > more build capacity for the "apache" github organization.
> > > > I hope we'll soon have quicker builds again.
> > > >
> > > > On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <
> > [hidden email]
> > > > <javascript:;>>
> > > > wrote:
> > > >
> > > > > That's good idea.
> > > > >
> > > > > Should be good to have mix of stable with Apache Jenkins for master
> > > > > and PRs, and Travis for individual forks.
> > > > >
> > > > > - Henry
> > > > >
> > > > > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <
> [hidden email]
> > > > <javascript:;>>
> > > > > wrote:
> > > > > > Hey!
> > > > > >
> > > > > > I would also like to continue using Travis but the current
> > situation
> > > is
> > > > > not
> > > > > > acceptable because we practically can't use Travis anymore for
> pull
> > > > > > requests or the current master. If it cannot be resolved then I
> > think
> > > > we
> > > > > > should move on.
> > > > > >
> > > > > > The builds service team [1] at Apache offers Jenkins [2] for
> > > continuous
> > > > > > integration. I think it should be fairly simple to set up. We
> could
> > > > still
> > > > > > use Travis in our forked repositories but have a reliable CI
> > solution
> > > > for
> > > > > > the master and pull requests.
> > > > > >
> > > > > > Max
> > > > > >
> > > > > > [1] https://builds.apache.org/
> > > > > > [2] http://jenkins-ci.org
> > > > > >
> > > > > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
> > > > > [hidden email] <javascript:;>>
> > > > > > wrote:
> > > > > >
> > > > > >> I also like the travis infrastucture. Thanks for bringing this
> up
> > > and
> > > > > >> reaching out to the travis guys.
> > > > > >>
> > > > > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <
> > > [hidden email]
> > > > <javascript:;>>
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hi guys,
> > > > > >> >
> > > > > >> > the build queue on travis is getting very very long. It seems
> > that
> > > > it
> > > > > >> takes
> > > > > >> > 4 days now until commits to master are build. The nightly
> builds
> > > > from
> > > > > the
> > > > > >> > website and the maven snapshots are also delayed by that.
> > > > > >> > Right now,  there are 33 pull request builds scheduled (
> > > > > >> > https://travis-ci.org/apache/flink/pull_requests), and 8
> builds
> > > on
> > > > > >> master:
> > > > > >> > https://travis-ci.org/apache/flink/builds.
> > > > > >> >
> > > > > >> > The problem is that travis accounts are per github user. In
> our
> > > > case,
> > > > > the
> > > > > >> > user is "apache", so all ASF projects that have travis enabled
> > > > share 5
> > > > > >> > concurrent builders.
> > > > > >> >
> > > > > >> > I would actually like to continue using Travis.
> > > > > >> >
> > > > > >> > The easiest option is probably asking travis if they can give
> > the
> > > > > >> "apache"
> > > > > >> > user more build capacity.
> > > > > >> >
> > > > > >> > If thats not possible, we have to look into other options.
> > > > > >> >
> > > > > >> >
> > > > > >> > I'm going to ask Travis if they can do anything about it.
> > > > > >> >
> > > > > >> > Robert
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
>

[Robert Metzger]

Now there is a blog post on the update:
https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci
It seems that Apache now has 30 concurrent builds and is a paying Travis
user/customer.

On Thu, Apr 2, 2015 at 3:58 PM, Robert Metzger <[hidden email]> wrote:

> I just found out that the execution time limit for the container-based
> infra (the one we're using) is 120 minutes ;)
> So we have some room left to write more test ;) (But please don't overdo
> it )
>
> On Tue, Mar 31, 2015 at 11:32 AM, Maximilian Michels <[hidden email]>
> wrote:
>
>> Very nice. Thanks Robert!
>>
>> On Mon, Mar 30, 2015 at 9:13 PM, Robert Metzger <[hidden email]>
>> wrote:
>>
>> > It seems that the issue is fixed. I've just pushed two times to a pull
>> > request and it immediately started building both.
>> > I think the "apache" user has much more parallel builds available now
>> (we
>> > don't have any builds queuing up anymore).
>> >
>> > On Thu, Mar 26, 2015 at 4:06 PM, Henry Saputra <[hidden email]
>> >
>> > wrote:
>> >
>> > > Awesome news!
>> > >
>> > > On Thursday, March 26, 2015, Robert Metzger <[hidden email]>
>> wrote:
>> > >
>> > > > Travis replied me with very good news: Somebody from INFRA was
>> asking
>> > the
>> > > > same question around the same time as I did and Travis is working on
>> > > adding
>> > > > more build capacity for the "apache" github organization.
>> > > > I hope we'll soon have quicker builds again.
>> > > >
>> > > > On Tue, Mar 24, 2015 at 4:42 PM, Henry Saputra <
>> > [hidden email]
>> > > > <javascript:;>>
>> > > > wrote:
>> > > >
>> > > > > That's good idea.
>> > > > >
>> > > > > Should be good to have mix of stable with Apache Jenkins for
>> master
>> > > > > and PRs, and Travis for individual forks.
>> > > > >
>> > > > > - Henry
>> > > > >
>> > > > > On Tue, Mar 24, 2015 at 8:03 AM, Maximilian Michels <
>> [hidden email]
>> > > > <javascript:;>>
>> > > > > wrote:
>> > > > > > Hey!
>> > > > > >
>> > > > > > I would also like to continue using Travis but the current
>> > situation
>> > > is
>> > > > > not
>> > > > > > acceptable because we practically can't use Travis anymore for
>> pull
>> > > > > > requests or the current master. If it cannot be resolved then I
>> > think
>> > > > we
>> > > > > > should move on.
>> > > > > >
>> > > > > > The builds service team [1] at Apache offers Jenkins [2] for
>> > > continuous
>> > > > > > integration. I think it should be fairly simple to set up. We
>> could
>> > > > still
>> > > > > > use Travis in our forked repositories but have a reliable CI
>> > solution
>> > > > for
>> > > > > > the master and pull requests.
>> > > > > >
>> > > > > > Max
>> > > > > >
>> > > > > > [1] https://builds.apache.org/
>> > > > > > [2] http://jenkins-ci.org
>> > > > > >
>> > > > > > On Tue, Mar 24, 2015 at 3:46 PM, Márton Balassi <
>> > > > > [hidden email] <javascript:;>>
>> > > > > > wrote:
>> > > > > >
>> > > > > >> I also like the travis infrastucture. Thanks for bringing this
>> up
>> > > and
>> > > > > >> reaching out to the travis guys.
>> > > > > >>
>> > > > > >> On Tue, Mar 24, 2015 at 3:38 PM, Robert Metzger <
>> > > [hidden email]
>> > > > <javascript:;>>
>> > > > > >> wrote:
>> > > > > >>
>> > > > > >> > Hi guys,
>> > > > > >> >
>> > > > > >> > the build queue on travis is getting very very long. It seems
>> > that
>> > > > it
>> > > > > >> takes
>> > > > > >> > 4 days now until commits to master are build. The nightly
>> builds
>> > > > from
>> > > > > the
>> > > > > >> > website and the maven snapshots are also delayed by that.
>> > > > > >> > Right now,  there are 33 pull request builds scheduled (
>> > > > > >> > https://travis-ci.org/apache/flink/pull_requests), and 8
>> builds
>> > > on
>> > > > > >> master:
>> > > > > >> > https://travis-ci.org/apache/flink/builds.
>> > > > > >> >
>> > > > > >> > The problem is that travis accounts are per github user. In
>> our
>> > > > case,
>> > > > > the
>> > > > > >> > user is "apache", so all ASF projects that have travis
>> enabled
>> > > > share 5
>> > > > > >> > concurrent builders.
>> > > > > >> >
>> > > > > >> > I would actually like to continue using Travis.
>> > > > > >> >
>> > > > > >> > The easiest option is probably asking travis if they can give
>> > the
>> > > > > >> "apache"
>> > > > > >> > user more build capacity.
>> > > > > >> >
>> > > > > >> > If thats not possible, we have to look into other options.
>> > > > > >> >
>> > > > > >> >
>> > > > > >> > I'm going to ask Travis if they can do anything about it.
>> > > > > >> >
>> > > > > >> > Robert
>> > > > > >> >
>> > > > > >>
>> > > > >
>> > > >
>> > >
>> >
>>
>
>