gosu does not appear to be effective with native OS-X docker. Containers seem to run as root:root no matter what. Investigation needed.

Add auto build/validate/push to samsung-cnct/goglide:
via Jenkins.

For clarity of use and ease of maintenance, have two separate repositories:

• goglide build repository (maintains the build tool for golang)
• example-project repository (provides a basic golang app that uses the above container to build itself)

Suggestion:

Namespace the repositories under the solas repositories, e.g. solas-golang-container and solas-golang-app.

Having these two functionalities be top-level repositories should also come with their own, workable gitlab CI runs. Manual builds and pushes should be automated.

With the solas template repositories come step-by-step instructions on how to get a new, immediately workable project up and running. This project should match.

• Provide use-case and purpose of project
• Explain what the project provides (i.e. it provides a setup for a certain kind of golang project? It builds a command line tool?)
• Provide step-by-step, complete instructions on how to copy the template and customize it (look at instructions for solas-container for an example).

when complete, please check off goglide-rel on https://github.com/samsung-cnct/issues/issues/89#issuecomment-343000090

The purpose of the goglide container is to use it to build go binaries in a controlled way. Adding instructions for local development are prone to result in erroneous behavior.

Remove any ambiguities/support for locally building these tools.

Go has the dep package to manage dependencies:
https://github.com/Masterminds/glide#golang-dep

Investigate whether goglide-container should be using dep instead.

Create an Example golang Project Setup for new projects to start with.

README
DEVELOPMENT
Makefile
build.sh
make.golang

Explain structure, and which tools to use and why.
requirements for consideration of a clean build etc.

In build.sh clarify the path needed for go_dir. Also make it clear that if you have go tools installed for building on your mac (OSX) the GOPATH needs to be separate from the GOPATH for linux development.

In Jenkinsfile, correct the directory for containerize and push. Also separate out the vet stages to vet and lint.

I'm thinking we should comment out the gosimple test too, what do you think?