[
https://issues.apache.org/jira/browse/BEAM-6907?focusedWorklogId=290828&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-290828
]
ASF GitHub Bot logged work on BEAM-6907:
----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Aug/19 22:42
Start Date: 07/Aug/19 22:42
Worklog Time Spent: 10m
Work Description: markflyhigh commented on pull request #9277:
[BEAM-6907] Reuse Python tarball in tox & dataflow integration tests
URL: https://github.com/apache/beam/pull/9277#discussion_r311792100
##########
File path:
buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy
##########
@@ -1884,6 +1884,13 @@ class BeamModulePlugin implements Plugin<Project> {
}
}
}
+ // Set run order for basic tasks.
+ // This should be called after applyPythonNature() since TaskContainer
+ // requires task instances created first before setting the order.
+ project.ext.setTaskOrder = {
Review comment:
You are right, set `setupVirtualenv`run after `installGcpTest` is not
required in here. The main purpose is to set `installGcpTest` run after
`sdks:python:sdist` in each project.
I don't know if depend on `distTarBall` will work or not but worth to try,
so that we may be able to get rid of `setTaskOrder`
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 290828)
Time Spent: 2h 20m (was: 2h 10m)
> 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: 2h 20m
> 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)
