You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Tim Robertson (JIRA)" <ji...@apache.org> on 2018/05/24 09:46:00 UTC

[jira] [Assigned] (BEAM-3249) Use Gradle to build/release project

     [ https://issues.apache.org/jira/browse/BEAM-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Robertson reassigned BEAM-3249:
-----------------------------------

    Assignee: Tim Robertson  (was: Luke Cwik)

> Use Gradle to build/release project
> -----------------------------------
>
>                 Key: BEAM-3249
>                 URL: https://issues.apache.org/jira/browse/BEAM-3249
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system, testing
>            Reporter: Luke Cwik
>            Assignee: Tim Robertson
>            Priority: Major
>          Time Spent: 14h 20m
>  Remaining Estimate: 0h
>
> I have collected data by running several builds against master using Gradle and Maven without using Gradle's support for incremental builds.
> Gradle (mins)
> min: 25.04
> max: 160.14
> median: 45.78
> average: 52.19
> stdev: 30.80
> Maven (mins)
> min: 56.86
> max: 216.55
> median: 87.93
> average: 109.10
> stdev: 48.01
> I excluded a few timeouts (240 mins) that happened during the Maven build from its numbers but we can see conclusively that Gradle is about twice as fast for the build when compared to Maven when run using Jenkins.
> Original dev@ thread: https://lists.apache.org/thread.html/225dddcfc78f39bbb296a0d2bbef1caf37e17677c7e5573f0b6fe253@%3Cdev.beam.apache.org%3E
> The data is available here https://docs.google.com/spreadsheets/d/1MHVjF-xoI49_NJqEQakUgnNIQ7Qbjzu8Y1q_h3dbF1M/edit?usp=sharing



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