[
https://issues.apache.org/jira/browse/BEAM-6907?focusedWorklogId=289986&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-289986
]
ASF GitHub Bot logged work on BEAM-6907:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Aug/19 20:48
Start Date: 06/Aug/19 20:48
Worklog Time Spent: 10m
Work Description: markflyhigh commented on issue #9277: [BEAM-6907] Reuse
Python tarball in tox & dataflow integration tests
URL: https://github.com/apache/beam/pull/9277#issuecomment-518838159
Run Python Dataflow ValidatesRunner
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 289986)
Time Spent: 0.5h (was: 20m)
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
