[
https://issues.apache.org/jira/browse/BEAM-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Liu updated BEAM-6907:
---------------------------
Description:
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
was:
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 per version per runner.
- Group basic tasks that are used in most projects in BeamModulePlugins.
- Avoid deeply nested directory structure for build.gradle.
> 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.3#76005)
