[
https://issues.apache.org/jira/browse/BEAM-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895501#comment-16895501
]
Mark Liu edited comment on BEAM-6907 at 7/29/19 6:19 PM:
---------------------------------------------------------
We already have https://issues.apache.org/jira/browse/BEAM-7675 tracking
configuration restructure and use this one to focus on reusing tar build in
integration tests.
was (Author: markflyhigh):
We already have https://issues.apache.org/jira/browse/BEAM-7675 tracking
configuration structure and use this one to focus on reusing tar build in
integration tests.
> Standardize Gradle projects/tasks structure for Python SDK
> ----------------------------------------------------------
>
> Key: BEAM-6907
> URL: https://issues.apache.org/jira/browse/BEAM-6907
> Project: Beam
> Issue Type: Task
> Components: build-system
> Reporter: Mark Liu
> Assignee: Mark Liu
> Priority: Major
>
> As Gradle parallelism applied to Python tests and more python versions added
> to tests, the way Gradle manages projects/tasks changed a lot. Frictions are
> generated during Gradle refactor since some projects defined separate build
> script under source directory. Thus, It will be better to standardize how we
> use Gradle. This will help to manage Python tests/builds/tasks across
> different versions and runners, and also easy for people to learn/use/develop.
> In general, we may want to:
> - Apply parallel execution
> - Share common tasks
> - Centralize test related tasks
> - Have a clear Gradle structure for projects/tasks
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
