[
https://issues.apache.org/jira/browse/STORM-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692874#comment-14692874
]
Jungtaek Lim commented on STORM-986:
------------------------------------
[~caofangkun]
http://docs.travis-ci.com/user/caching/
Caching directories is only available for private repos., and container-based
infrastructure.
I already experiment container based build, but unfortunately it's slower than
previous.
- Legacy : https://travis-ci.org/HeartSaVioR/storm/builds/70504611
- Container : https://travis-ci.org/HeartSaVioR/storm/builds/70501263
I wrote some mails to investigate it with Travis CI support team, but
unfortunately it was end up with standing on legacy way.
So we can't apply this enhancement for now unless Travis CI find a way to
resolve it.
ps. Here's the mails I've talked with.
{quote}
Hi, Travis team.
I'm experimenting new container based build, and found build is slower than
previous.
Legacy: https://travis-ci.org/HeartSaVioR/storm/builds/70504611
Container based: https://travis-ci.org/HeartSaVioR/storm/builds/70501263
Faster starting build is really great, but CPU power seems to be lower.
Is it normal, and if it's abnormal, could you fix it?
Best,
Jungtaek Lim (HeartSaVioR)
{quote}
{quote}
Hi Jungtaek,
Thanks for getting in touch and sorry about the delay. We've found that builds
with heavy disk IO have suffered the most, as the legacy Linux infrastructure
includes a tmpfs mount at /tmp, whereas doing the same for container-based is
not straightforward and hasn't yet been implemented. Is there a chance that
your project is doing a high number of disk iops?
Cheers,
How would you rate my reply?
Great Okay Not Good
--
Daniel Buch
[email protected]
{quote}
{quote}
Hi Daniel,
During build, we wrote stdout logs to file because of stdout length limitation
of Travis CI, and it is somewhat bigger.
I've just run test which redirects stdout to log file (monitored with OSX
iostat), and it often shows over 300~500 tps while running unit tests, not
compiling.
Maybe I may want to stick legacy build, and migrate to container build later.
It would be more appreciated when I will be noticed about news about this.
Thanks,
Jungtaek Lim (HeartSaVioR)
{quote}
{quote}
Hi Jungtaek,
I agree that it's probably best to stick to the standard Linux infrastructure
for now. We have some exciting changes in the works that may address this
particular issue, which we'll likely announce via the blog
(http://blog.travis-ci.com/) as well as Twitter (https://twitter.com/travisci).
Thanks for your patience!
Cheers,
How would you rate my reply?
Great Okay Not Good
--
Daniel Buch
[email protected]
{quote}
> Caching maven dependencies to speedup CI builds
> -----------------------------------------------
>
> Key: STORM-986
> URL: https://issues.apache.org/jira/browse/STORM-986
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: caofangkun
> Assignee: caofangkun
> Priority: Trivial
>
> See: http://docs.travis-ci.com/user/caching/
> Modify
> {code}
> diff --git a/.travis.yml b/.travis.yml
> index a7e2df4..d6e3c8b 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -13,6 +13,9 @@ language: java
> jdk:
> - oraclejdk7
> - oraclejdk8
> +cache:
> + directories:
> + - $HOME/.m2/repository
> before_install:
> - rvm use 2.1.5 --install
> - nvm install 0.12.2
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
