It's going to be a fun discussion. The most obvious questions have been
brought up already: Release cycles and API stability towards usage by code
in other repositories.
Looking forward :-)
On Thu, Dec 15, 2016 at 11:48 AM, Till Rohrmann
wrote:
> I'm in favour of splitting the project up into m
I'm in favour of splitting the project up into multiple repositories. This
will decrease building and testing time locally as well as on Travis. The
downside, however, will be that if not built together, conflicting changes
between different modules might go unnoticed until the release or the next
Thanks for the insight, Robert.
I have new MacbookPro so I think should have enough CPU to build.
Seemed like the long time taken mostly on shading and pulling the world
(dependencies)
Do you have anything in your settings.xml to set the updatePolicy for
central repo?
- Henry
On Wed, Dec 14, 2
I am starting to think that we should go a step further from "build
profiles".
How about splitting the repository up into multiple repositories that can
be built independently? We could for example do
- flink-core (core, apis, runtime, clients)
- flink-libraries (gelly, ml, cep, table, scala s
On my machine, I need ~10 minutes to do a clean install without tests. Not
sure what is causing the slow builds in your environment.
I think our builds are both IO (shading) and CPU (Scala compiler)
intensive. If one is not well equipped you'll have these build times.
I contacted the Travis suppor
Building Flink from root now takes long time due to more and more modules
that we have =(
For me if takes about 50 minutes or more when doing "mvn clean install
-DskipTests"
Should we start adding Maven profiles to help exclude some Maven modules,
like connectors and flink-libraries by default ?
I also just noticed it today. We used to work with the 120 minutes limit and
the builds took way longer as you said. I don't know what's going on here...
It might be related to some issues they reported a few hours ago
(https://twitter.com/traviscistatus), but I can't tell.
I really hope that t
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 wrote:
> I just found out that the execution time
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 wrote:
> Very nice. Thanks Robert!
>
> On Mon, M
Very nice. Thanks Robert!
On Mon, Mar 30, 2015 at 9:13 PM, Robert Metzger 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 a
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
wrote:
> Aw
Awesome news!
On Thursday, March 26, 2015, Robert Metzger 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 so
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
wrote:
> No, but we can ask David Nalley from Infra, he is talking to them.
>
> On Thu, Mar
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 wrote:
> That's nice to hear. They didn't specify any time frame?
>
> On Thu, Mar 26, 2015 at 9:25 AM, Fabian Hueske wrote:
>
> > Great!
> > Thanks Robert for sharing the good
That's nice to hear. They didn't specify any time frame?
On Thu, Mar 26, 2015 at 9:25 AM, Fabian Hueske wrote:
> Great!
> Thanks Robert for sharing the good news :-)
>
> 2015-03-26 9:08 GMT+01:00 Robert Metzger :
>
> > Travis replied me with very good news: Somebody from INFRA was asking the
> >
Great!
Thanks Robert for sharing the good news :-)
2015-03-26 9:08 GMT+01:00 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 org
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 Saputr
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 wrote:
> Hey!
>
> I would also like to continue using Travis but the current situation is not
> acceptable
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] fo
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 wrote:
> I would also like to continue u
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, Rob
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 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.
22 matches
Mail list logo
