beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-3249) Use Gradle to build/release project
Date Fri, 09 Mar 2018 18:14:00 GMT


ASF GitHub Bot logged work on BEAM-3249:

                Author: ASF GitHub Bot
            Created on: 09/Mar/18 18:13
            Start Date: 09/Mar/18 18:13
    Worklog Time Spent: 10m 
      Work Description: lukecwik commented on issue #4830: [BEAM-3249, BEAM-3457] Make Apache
Rat a dependency of the Java and Gradle precommits.
   Swapped to `:sdks:java:core:buildNeeded` and `:sdks:java:core:buildDependents` to prevent
a regression if the SDK core ever depends on another project like the shaded guava module
that had been discussed.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 78962)
    Time Spent: 3h 20m  (was: 3h 10m)

> Use Gradle to build/release project
> -----------------------------------
>                 Key: BEAM-3249
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system, testing
>            Reporter: Luke Cwik
>            Assignee: Luke Cwik
>            Priority: Major
>          Time Spent: 3h 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:
> The data is available here

This message was sent by Atlassian JIRA

View raw message