[
https://issues.apache.org/jira/browse/AVRO-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250035#comment-14250035
]
Tom White commented on AVRO-1537:
---------------------------------
> It would be great if one could easily use this to create tag and branch
> workspaces in addition to trunk. Can we somehow pass a parameter to indicate
> this?
After {{docker run -it avro-build}} you can do tagging/branching from the
command line. If you use the -v option then you can use the same Avro workspace
that you have checked out locally, which is probably the most useful option.
> Why check out from both SVN and git? Is that just for exemplary purposes?
Yes. You need SVN to run {{./build.sh dist}} since it does an svn export. Lots
of people use git for development so I added that. Maybe I should just remove
these lines (as Niels suggests too).
> Might we somehow use this to create a release-building script?
Definitely, that would be a good thing to aim for. We'd need to fix the tests
first.
> 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)
