search

linkedin / dynamometer

A tool for scale and performance testing of HDFS with a specific focus on the NameNode.
BSD 2-Clause "Simplified" License
131 stars 34 forks source link

Bumped Gradle and removed the workaround #87

Closed mockitoguy closed 5 years ago

mockitoguy commented 5 years ago

I bumped to latest 4.x version and it resolves the problem. I put back the original Shipkit settings.

mockitoguy commented 5 years ago

No worries!

xkrogen commented 5 years ago

I had to revert this as it was causing the build to completely be unable to read any property specified within the bintray closure:

[performRelease] > Task :dynamometer-blockgen:bintrayUpload
[performRelease] :dynamometer-blockgen:bintrayUpload - publishing to Bintray
[performRelease]   - dry run: false, publish: true, version: 0.1.2, Maven Central sync: true
[performRelease]   - user/org: null/null, repository/package: null/com.linkedin.dynamometer
[performRelease] Repository name, package name or version name are null for project: project ':dynamometer-blockgen'
[performRelease]

(all of the specified properties are getting read as null)

Build link here: https://travis-ci.org/linkedin/dynamometer/jobs/500652004