Golang Plugins Tooling and Development

[mattyjones]

What tools do we want to use for building? (gox, go build)

What tools do we want to use for testing? (go vet, golint, goconvey)

What type of artifacts do we want to release? (tarball, rpm, deb, chocolatey)

Do we fully support Sensu1 and Sensu2? (y/n, thoughts?)

What platforms and/or architectures do we build and support for? (linux, bsd, aix, win)

Are you a golang developer, curious about golang, or do you just want to use the plugins?

Additional tips and best practices specific to Golang.

[grepory]

This is a really fun discussion. I think our engineering team members might have some great ideas or useful/helpful input for y’all. If you’re up for it, maybe we can setup some time to discuss?

[majormoses]

I don't have a lot of experience with golang development but let me know when you want to get together to discuss it so that I can learn more about it and ensure that from a general maintenance stance we follow practices that will reduce burden on maintainers and follow the same base conventions such as changelogs, package management, etc.

[amdprophet]

Re: building - I was playing around with GoReleaser for automatically building binaries for each GOOS / GOARCH combination https://github.com/amdprophet/system-profile-metrics. It seems to work quite well.