Add latest commit used used to build in /api/peers/version

[ghost]

{"success":true,"version":"0.5.0","build":"v06:02:05 30/11/2016\n"}
/api/peers/version

It's needed for Lisk Network Stats to use when there is not build info or just along with date to get exact version.

[Isabello]

There is only one release/build per revision. This is a waste to implement and creates no benefit.

…

On Tue, Dec 6, 2016 at 2:24 PM, Unhandled Exception < ***@***.***> wrote: {"success":true,"version":"0.5.0","build":"v06:02:05 30/11/2016\n"} /api/peers/version It's needed for Lisk Network Stats <https://github.com/karek314/lisk-network-reporter> to use when there is not build info or just along with date to get exact version. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#340>, or mute the thread <https://github.com/notifications/unsubscribe-auth/APzFsCc3znLrLppIQ-yjo85VFERgTGJmks5rFcRlgaJpZM4LF109> .

[ghost]

But there is no build informations specified when someone compile directly from repository and then statistics website is incomplete. This is relatively easy to implement.

[Isabello]

Can you give me an example or a pull request to implement this feature? I don't see it being easy unless we add functionality to check git log as part of core.

[ghost]

It can be done during building, stored in config then easily accessible by node. I think this is simplest approach.

[Isabello]

we dont build the client if we run from source. so the build file is never populated on a source configured node.

[ghost]

There are few other ways
https://stackoverflow.com/questions/34518389/get-hash-of-most-recent-git-commit-in-node