Emitting version metrics also adding a githook that runs a script the automatically updates the version unless the user manually skips

[allenchen2244]

Adding version into the build_info metric gauge.

Played around with metrics on grafana should be able to add a graph in pretty easily once this is done.

Also added a script that updates a version number with a timestamp if there's no manual update the major or patch version.

Added a githook that ensures the user is aware that they're updating the version or skipping it entirely if it's something really small

[davidporter-id-au]

Can we add a makefile step or some other test step to ensure this doesn't get out of sync with the tagged release? @Groxx does this seem insane?

[allenchen2244]

I think Stephen/Ender was saying that the tag version being the last and all the way to do it is to make sure we update the release steps to update this version with every branch since the version itself isn't accessible.

[davidporter-id-au]

I mean something like make test also doing a grep for this value and ensuring it's not out of sync with the tag

[Groxx]

late to the game, but:
unfortunately I don't think there's a way to automate this, short of automating releases entirely... which brings other major complications too. though we might do that eventually.

for environments that use go modules (i.e. not our internal monorepo, at least currently), we could pull this information from the module's build-time metadata, which is probably the best option. that's always up to date.

for non-module environments... dunno.

[coveralls]

Pull Request Test Coverage Report for Build 01843a8e-0849-4c88-849e-1f372e273338

• 6 of 6 (100.0%) changed or added relevant lines in 1 file are covered.
• 128 unchanged lines in 18 files lost coverage.
• Overall coverage decreased (-0.07%) to 57.28%

---

Files with Coverage Reduction	New Missed Lines	%
client/history/client.go	2	38.1%
client/history/metricClient.go	2	45.3%
common/membership/hashring.go	2	83.54%
common/persistence/executionManager.go	2	78.83%
common/task/fifoTaskScheduler.go	2	84.54%
service/history/handler.go	2	47.17%
common/persistence/serialization/parser.go	4	65.41%
common/persistence/serialization/thrift_decoder.go	4	61.22%
service/frontend/workflowHandler.go	4	59.98%
common/persistence/statsComputer.go	5	94.64%

Totals
Change from base Build 018439f9-7d82-4142-b1f9-aa629405d4a7:	-0.07%
Covered Lines:	85177
Relevant Lines:	148702

---

💛 - Coveralls

[davidporter-id-au]

Please update the commit summary to include:

The problem:

That figuring out what the open-source version is doing for emitted metrics is hard, and this is a change to expose the open-source version as a snapshot to logs, metrics etc. It'll help operationally to understand what's running where.

The solution

1. The proposal you're putting here - tl;dr that we're adding a timestamp-based patch-version which is exposed at runtime which is hooked in to commits and bumped automatically (perhaps surprising)
2. A callout that this requires git config core.hooksPath .githooks to manually be run

Potentially this will be annoying / not work for some build or pipeline or other edge-case that