Include the commit version in the served websites

[niccokunzmann]

As a contributor, I would like to see when my patch goes life. Thus, I would like to know, which commit it is that is served.

Two possible solutions:

• include the commit of all services in the html page as a comment.
• Use a tag for each sever online i.e. node1 which points to the git commit used by this node.

[Wardormeur]

We can't use gulp to generate this as 1 µs can be updated without the others (zen won't be redeployed), so it means every µs must have an endpoint exposing its commit so that zen can list, through a dedicated page, the commits of each µs. Not too hard, just a bit of a pain. Also consider that there is a load-balancer in front of it, meaning the 2 instances (shouldn't, but) could display different versions, depending on which instance you fall on. @DanielBrierton Aren't the CircleCI builds open to anybody ?

[butlerx]

https://circleci.com/gh/CoderDojo

[DanielBrierton]

We should probably add this build badge to the README.md of each project so it can be easily found.

[niccokunzmann]

Sure, let's create a beginner issue :)

[Wardormeur]

It doesn't tell though if it's a merge or a PR test, so you have to dig into the test to see if it was deployed/n Edit : nvmd, dumb