[
https://issues.apache.org/jira/browse/AVRO-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254119#comment-15254119
]
Ryan Blue commented on AVRO-1705:
---------------------------------
Is this the right approach to CI?
I think we should consider per-implementation runs. While it's great to be able
to do checks on all of the languages easily and at one time, we don't need to
waste time and resources building and testing all languages when there's a
change to just one.
At the same time, we should be doing more thorough testing for some
implementations, like Ruby. We ran into issues last release where some Ruby
versions had test failures, but Ruby has tooling built around testing packages
in multiple versions we could be using (and arguably should be).
What do you guys think about having multiple profiles to do better testing for
each implementation?
> Set up Jenkins job to test all languages using Docker
> -----------------------------------------------------
>
> Key: AVRO-1705
> URL: https://issues.apache.org/jira/browse/AVRO-1705
> Project: Avro
> Issue Type: Task
> Components: build
> Affects Versions: 1.7.7
> Reporter: Tom White
> Priority: Critical
> Labels: starter
>
> The ASF Jenkins instance now supports Docker (BUILDS-25), so we could run all
> the tests (for all languages that Avro supports) using the Avro Dockerfile.
> We might also do a nightly build of the whole distribution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
