On 11/20/2014 02:11 AM, Tom Dunstan wrote:
On Thu, Nov 20, 2014 at 2:03 AM, Mikolaj Izdebski mizdebsk@redhat.com wrote:
This should definitely be improved, but I will wait for upstream input
how these fields should look like in Fedora gradle RPM package.
Great work Mokilaj!
We reckon that setting the build number to something like 'fedora22-3' where 3 is the rpm spec version would probably do the trick. If someone pops up with a weird error in our forums, we'll probably ask them to run gradle --version anyway and the build number is right there at the top.
So leave the version number as whatever the release version number is and set the build number to something identifiable.
I've included full Fedora package release number in Gradle build number. Now gradle --version prints:
------------------------------------------------------------ Gradle 2.2 ------------------------------------------------------------
Build time: 2014-11-20 10:38:24 UTC Build number: Fedora 2.2-2.fc22 Revision: <unknown>
Groovy: 2.3.7 Ant: Apache Ant(TM) version 1.9.4 compiled on August 11 2014 JVM: 1.8.0_40 (Oracle Corporation 25.40-b16) OS: Linux 3.16.7-200.fc20.x86_64 amd64
And build-receipt.properties contains:
buildNumber=Fedora 2.2-2.fc22 buildTimestamp=20141120103824+0000 commitId=<unknown> hostname=buildvm-07.phx2.fedoraproject.org isSnapshot=false javaVersion=1.8.0_40 osName=Linux osVersion=3.17.2-200.fc20.x86_64 project=gradle rcNumber= username=mockbuild versionBase=2.2 versionNumber=2.2
To fix host name I had to apply a patch, which I submitted as PR: https://github.com/gradle/gradle/pull/354