You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Zameer Manji (JIRA)" <ji...@apache.org> on 2015/12/28 03:45:49 UTC
[jira] [Resolved] (AURORA-959) Simplify python builds
[ https://issues.apache.org/jira/browse/AURORA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zameer Manji resolved AURORA-959.
---------------------------------
Resolution: Cannot Reproduce
I cannot reproduce this issue on master:
{noformat}
$ find . -name BUILD | xargs grep python_library | wc -l
31
{noformat}
> Simplify python builds
> ----------------------
>
> Key: AURORA-959
> URL: https://issues.apache.org/jira/browse/AURORA-959
> Project: Aurora
> Issue Type: Story
> Components: Client, Executor
> Reporter: Bill Farner
> Priority: Minor
>
> In total, the python builds have approximately 111 build targets:
> {noformat}
> $ find . -name BUILD | xargs grep python_library | wc -l
> 111
> {noformat}
> These make up 3143 lines of BUILD configuration:
> {noformat}
> $ find . -name BUILD | xargs wc -l | grep total
> 3143 total
> {noformat}
> AFAICT the only upside to this splitting is for scoping unit tests. I suggest we lean harder on our build tooling to provide this support rather than maintaining all this extra configuration.
> Given that we only have a handful of true top-level build targets, i suggest we significantly simplify this to minimize the number of targets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)