You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Mark Liu (JIRA)" <ji...@apache.org> on 2019/03/25 22:48:00 UTC

[jira] [Created] (BEAM-6907) Standardize Gradle projects/tasks structure for Python SDK

Mark Liu created BEAM-6907:
------------------------------

             Summary: 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


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.



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