Can we standardize the time zone of the "gradle --version" output?


(Matias Bjarland) #1

I was just trying to debug why my build was behaving differently on our ci server vs on my local dev box. One suspect was potentially different snapshot versions of the M5 release.

Output on ci server:

  jenkins@gloin:~/frameworks/gradle$ gradle --version

------------------------------------------------------------ Gradle 1.0-milestone-5 ------------------------------------------------------------

Gradle build time: Monday, October 24, 2011 8:56:08 PM PDT Groovy: 1.7.10 Ant: Apache Ant™ version 1.8.2 compiled on December 20 2010 Ivy: 2.2.0 JVM: 1.6.0_22 (Sun Microsystems Inc. 17.1-b03) OS: Linux 2.6.32-308-ec2 i386

output on dev box:

  nadurra:Homebrew root# gradle --version

 ------------------------------------------------------------  Gradle 1.0-milestone-5  ------------------------------------------------------------

 Gradle build time: Tuesday, October 25, 2011 5:56:08 AM CEST  Groovy: 1.7.10  Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010  Ivy: 2.2.0  JVM: 1.6.0_26 (Apple Inc. 20.1-b02-383)  OS: Mac OS X 10.7.2 x86_64  

note the apparently differing dates? Would easily make you think these are different builds. Turns out these two are the same exact distribution, the dates are just printed in different time zones.

Could we print out the date in a specific time zone or add a build number or some other way of visually identifying an exact build of gradle in the --version output?


(Leonard Brünings) #2

It would make sense to use UTC here.


(Luke Daley) #3

Done.

https://github.com/gradle/gradle/commit/c9c0f54604e214b8c4b331dee8d7f246afa71a95


(Leonard Brünings) #4

That was fast, thumbs up


(Matias Bjarland) #5

: )

if you guys ever end up having any Gradle events in Sweden I’ll buy you a round of beers.

That is one fast turn around…


(Luke Daley) #6

No problems at all.

And I’ll hopefully get to take you up on that offer one day.