[
https://issues.apache.org/jira/browse/AVRO-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975150#comment-16975150
]
Ryan Skraba commented on AVRO-2630:
-----------------------------------
Some ideas:
* Compile one travis job per language (a bit more feedback on failures,
possible parallelization).
* Reusing docker image/layers between jobs (can be a bit complicated without a
docker registry to push/pull). Including JDK8 and JDK11 in the same image for
a single build?
* Reusing a {{~/.m2}} cache between jobs and the docker image for release
artifacts.
There are surely some built-in functions to help out included in Yetus, but I'm
still near the bottom of that learning curve.
> Travis build is nearing timeout limits.
> ---------------------------------------
>
> Key: AVRO-2630
> URL: https://issues.apache.org/jira/browse/AVRO-2630
> Project: Apache Avro
> Issue Type: Improvement
> Components: build
> Reporter: Ryan Skraba
> Priority: Major
>
> Single "jobs" on travis are [limited to 50
> minutes|https://docs.travis-ci.com/user/customizing-the-build/#build-timeouts].
> A "normal" build takes 47-48 minutes and can occasionally bump over the
> limit, causing timeout errors.
> We can see that this happens occasionally on master and on pull requests.
> We should find a strategy to limit the length of time for a of the jobs being
> run.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
