JB - for your comparison, please also omit cross-compiling all the Go
examples because they are only built using Gradle.
On Tue, May 1, 2018 at 8:59 AM Jean-Baptiste Onofré wrote:
> Thanks for the update Kenn, that makes sense.
>
> I'm checking the artifacts generated by Gradle right now.
>
>
Thanks for the update Kenn, that makes sense.
I'm checking the artifacts generated by Gradle right now.
Regards
JB
On 01/05/2018 17:42, Kenneth Knowles wrote:
Raw execution time for tasks from clean is not the only thing to test. I
would say it is not even important. Try these from clean:
Raw execution time for tasks from clean is not the only thing to test. I
would say it is not even important. Try these from clean:
- Gradle: ./gradlew :beam-sdks-java-io-mongodb:test && ./gradlew :
beam-sdks-java-io-mongodb:test
- Maven: mvn -pl sdks/java/io/mongodb test -am && mvn -pl
sdks/java
Thanks, for me, Maven 3.5.2 takes quite the same time than Gradle (using
the wrapper). It's maybe related to my environment.
Anyway, I'm doing a complete build review both in term of building time,
and equivalence (artifacts publishing, test, plugin execution).
I will provide an update soon.
Luke did gather data which showed that on our Jenkins executors the Gradle
build was much faster than the Maven build. Also right now we have
incremental builds turned off, but once we're confident enough to enable
them (at least for local development) that will often drop build times a
lot.
On Tu
By the way, I'm curious: did someone evaluate the build time gap between Maven
and Gradle ? One of the main reason to migrate to Gradle was the inc build and
build time. The builds I have launched are quite the same in duration. I will do
deeper tests to evaluate the gap.
Regards
JB
On 05/01/2018
Hi Scott,
thanks for the update! Just a clarification about IO performance tests:
those were fully migrated in Beam and all task necessary for running them
are there but Jenkins jobs still run mvn commands. This is due the fact
that PerfkitBenchmarker code (which is invoked by Jenkins and construc
Hi Scott
While https://issues.apache.org/jira/plugins/servlet/mobile#issue/BEAM-4057
is open, gradle is a concurrent of maven but maven must stay the default
build tool cause gradle breaks users.
Le 1 mai 2018 01:59, "Scott Wegner" a écrit :
> Many many of you have been hacking diligently on t
Many many of you have been hacking diligently on the Gradle build, and I'm
happy to announce that we now have a fully-functioning Gradle build!
There's been a ton of progress since our last update [1]:
* Improved nightly snapshot release [2]
* Improve runner quickstarts [5] [11]
* Python post-comm
