go-bamboo-plugin

go-bamboo-plugin copied to clipboard

GOROOT ignored but required?

1

When I specifically configure the GOROOT to a non-default go install it uses "/usr/lib/golang/bin/go" anyways? If it's also going to use /usr/lib/golang/bin/go then why is the GOROOT field required.

andytsnowden

Process timeout setting

2

We are encountering some issues with this plugin. `2016-06-16 13:16:21,328 INFO [15-BAM::Local Agent 1::Agent:pool-30-thread-1] [TaskResultBuilder] CGA-LIS2-BP-16: Failing task since return code of [/usr/local/go/bin/go test -v ./...] was -1 while expected...

hernit

Can't pass several build flags

4

When using the build task (and possibly others) and supplying `-ldflags` (and presumably also `-asmflags`, `-gccgoflags`, `-gcflags`, `-tags` and `-toolexec`, all of which accept a quoted list of values), the...

alanraison

go test exits with non zero exit code, so test parser never runs when tests fail

6

I must be missing something - the go test task exits with non-zero when a test fails, this means the next task which is meant to be the test parser...

jeks313

Include screenshots, examples and step-by-step instructions .. any problems the end user might run into

edwinakatosh

Add build-time `go get -v` support to fetch binaries like Godep automatically and cache them for later use.

handcraftedbits

Rather than having separate tasks.

edwinakatosh

Instead of Clover support as in #4, create a merged `go tool cover -html` output file that can be (dynamically?) added to the build as an artifact.

handcraftedbits