[ 
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. Some frictions are 

It will be better to standardize how we use Gradle to manage Python 
tests/builds/tasks across different versions and runners.

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.

  was:
As Gradle parallelism applied to Python tests and more python versions added to 
tests, the way Gradle manages projects/tasks changed a lot. It will be better 
to standardize how we use Gradle to manage Python tests/builds/tasks across 
different versions and runners.

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. Some frictions 
> are 
> It will be better to standardize how we use Gradle to manage Python 
> tests/builds/tasks across different versions and runners.
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to