[
https://issues.apache.org/jira/browse/AVRO-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248477#comment-14248477
]
Niels Basjes commented on AVRO-1537:
------------------------------------
I'm just reading up on Docker and just had an Idea:
What if instead of doing {code}# Clone Avro
RUN git clone http://git.apache.org/avro.git
RUN svn checkout https://svn.apache.org/repos/asf/avro/trunk/ avro-trunk{code}
You used something like (warning: I just read about this command; I didn't have
time yet to try it out)
{code}
ONBUILD ADD . avro
{code}
See: https://docs.docker.com/reference/builder/#onbuild
That would add your local version of Avro (which will most likely contain the
change you're working on) to the container.
In that scenario you would be able to run all tests for all languages/version
on the patched code before submitting it.
> Make it easier to set up a multi-language build environment
> -----------------------------------------------------------
>
> Key: AVRO-1537
> URL: https://issues.apache.org/jira/browse/AVRO-1537
> Project: Avro
> Issue Type: Improvement
> Reporter: Martin Kleppmann
> Attachments: AVRO-1537.patch, AVRO-1537.patch
>
>
> It's currently quite tedious to set up an environment in which the Avro test
> suites for all supported languages can be run, and in which release
> candidates can be built. This is especially so when we need to test against
> several different versions of a programming language or VM (e.g.
> JDK6/JDK7/JDK8, Ruby 1.8.7/1.9.3/2.0/2.1).
> Our shared Hudson server isn't an ideal solution, because it only runs tests
> on changes that are already committed, and maintenance of the server can't
> easily be shared across the community.
> I think a Docker image might be a good solution, since it could be set up by
> one person, shared with all Avro developers, and maintained by the community
> on an ongoing basis. But other VM solutions (Vagrant, for example?) might
> work just as well. Suggestions welcome.
> Related resources:
> * Using AWS (setting up an EC2 instance for Avro build and release):
> https://cwiki.apache.org/confluence/display/AVRO/How+To+Release#HowToRelease-UsingAWSforAvroBuildandRelease
> * Testing multiple versions of Ruby in CI: AVRO-1515
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
