Return-Path: X-Original-To: apmail-avro-dev-archive@www.apache.org Delivered-To: apmail-avro-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 10C3A10C13 for ; Wed, 10 Dec 2014 16:57:13 +0000 (UTC) Received: (qmail 43537 invoked by uid 500); 10 Dec 2014 16:57:12 -0000 Delivered-To: apmail-avro-dev-archive@avro.apache.org Received: (qmail 43455 invoked by uid 500); 10 Dec 2014 16:57:12 -0000 Mailing-List: contact dev-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@avro.apache.org Delivered-To: mailing list dev@avro.apache.org Received: (qmail 43241 invoked by uid 99); 10 Dec 2014 16:57:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2014 16:57:12 +0000 Date: Wed, 10 Dec 2014 16:57:12 +0000 (UTC) From: "Tom White (JIRA)" To: dev@avro.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AVRO-1537) Make it easier to set up a multi-language build environment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AVRO-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241376#comment-14241376 ] Tom White commented on AVRO-1537: --------------------------------- Forgot to say that I based the Dockerfile on the one from HBase. In particular, the way that it bundles a JDK and Maven. > 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 > > > 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)