[go-nuts] git, golang and continuous integration

On Jan 18, 2015 6:59 PM, "Kevin Malachowski" wrote:

I haven't worked with gitlab at all, but it seems like a simple enough
problem to solve if you can't find a good existing solution. If you can
manage to get gitlab to just run "go build" and other parts of the go tool
then you might have the basic functionality youre looking for: if the tool
exits with 0 status and no output its a green, otherwise you should report
the output to the user and mark it red.

Also, I'm not sure if gofmt notes were just an example, but as far as I
know its more common to blindly accept gofmt's suggested style than to
cherry pick its suggestions. Usually just running it on each file you're
checking in is enough, but running it in diff mode and writing that to the
webpage for users to see modifications could also be useful.

--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

On Sunday, January 18, 2015 at 2:26:58 AM UTC-8, Sankar wrote:

Hi,

We have some code in a private git repository (hosted under a private
gitlab instance for now).

Does anyone have any experience with a FOSS, private (something that we
can host ourselves for the time being) continuous integration system for
golang projects ? At the minimum, we want to see: go build status, go test
coverage percentage, gofmt issues, icons in the gitlab project page
(similar to drone, coveralls etc. for github)

If the system could also highlight gofmt, go build errors on every merge
request of gitlab, that will also be amazing.

Has anyone tried a similar setup ?

Thanks

Sankar