Ask HN: How do you build your Golang based repo ?
Do you use Makefiles with Glide, dep, or other vendoring tools or are you experimenting with something else like Bazel ? What has been your experience ?
I like to separate design and code, from build and test, from deploy and monitoring. And I like change. And experimenting with new techniques. dep is definitely next, as well as prometheus.
The things that determine what tools you use are often external to language design itself. How your remote team handles its gitflow. Whether people prefer vim on a remote dev instance or Atom locally with github integration. Are you targeting app engine or container engine.
Regardless of the heterogeneity, having a canonical $GOROOT source tree and deploying binaries makes things much more flexible.
I'll just point to one recent discovery that is helping a lot at the moment and may be useful to other people: godoc for static analysis
You can check it out here: https://github.com/artpar/daptin
The build scripts are located here: https://github.com/daptin/daptin/tree/master/scripts
The current setup is recognised by travis and semaphoreci.