FWIW, I plan to delete all of my contrib scripts O(soon) -- maybe today.

There are a lot of things that are built and pushed as docker images one
time, and then left to bit-rot. Maybe we can extend the build scripts to
run through them and at least ensure they build?

On Wed, Jan 21, 2015 at 7:17 AM, Brian Grant notifications@github.com
wrote:

FWIW, I plan to delete all of my contrib scripts O(soon) -- maybe today.

Reply to this email directly or view it on GitHub
#3665 (comment)
.

+1. We shouldn't have code in the codebase that isn't built, or it will
just bitrot.

On Wed, Jan 21, 2015 at 2:03 PM, Tim Hockin notifications@github.com
wrote:

There are a lot of things that are built and pushed as docker images one
time, and then left to bit-rot. Maybe we can extend the build scripts to
run through them and at least ensure they build?

On Wed, Jan 21, 2015 at 7:17 AM, Brian Grant notifications@github.com
wrote:

FWIW, I plan to delete all of my contrib scripts O(soon) -- maybe today.

Reply to this email directly or view it on GitHub
<
#3665 (comment)

.

—
Reply to this email directly or view it on GitHub
#3665 (comment)
.

Sadly 'go test' is insular and won't run other kinds of tests, so is a poor substitute for a build system unless you are entirely monoglot, which we are not. We could make our test scripts find *_test.sh and run those, too and then just add a build_test.sh to each dir which just calls 'make'.