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

Posted to commits@samza.apache.org by "Shanthoosh Venkataraman (JIRA)" <ji...@apache.org> on 2018/09/15 04:13:00 UTC

[jira] [Commented] (SAMZA-1885) Improve samza build time.

    [ https://issues.apache.org/jira/browse/SAMZA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615594#comment-16615594 ] 

Shanthoosh Venkataraman commented on SAMZA-1885:
------------------------------------------------

1. Upgrade to gradle version: 4.7(changes in gradle.properties, gradle-wrapper.jar).
2. Enable gradle parallel builds.
3. Set maximumParallelForks to 15(Determines the maximum number of tests that gradle will run in parallel. By default this is set to 1). 
4. Fix the tests that cannot be run in parallel(TestsJobsResource, TestTaskResource).

 

> Improve samza build time.
> -------------------------
>
>                 Key: SAMZA-1885
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1885
>             Project: Samza
>          Issue Type: New Feature
>            Reporter: Shanthoosh Venkataraman
>            Assignee: Shanthoosh Venkataraman
>            Priority: Major
>
> Samza codebase currently uses gradle 2.8 (which was released in 2014) and builds the codebase serially executing each of the gradle tasks one at a time. Not taking advantage of recent gradle features has caused slow builds (taking around 15 minutes to build samza codebase locally). This  hampers the overall developer productivity within the team. Proposal is to have a fasten builds by a series of changes.



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