dentaku/woodpecker-helm3
1
0
Fork 0
Code Pull requests Releases Activity
woodpecker-helm3/go.mod

12 lines
306 B
Modula-2
Raw Normal View History

Initial config for building the plugin itself
2019-12-03 17:50:15 +00:00
module github.com/pelotech/drone-helm3
go 1.13
Very rough code that can `helm install` The recommended way to test code that uses exec.Cmd involves setting up a real exec.Cmd that invokes `go test` with additional arguments that fire off a specially-constructed test that behaves the way the mocked- out script would be expected to do. It's a sensible way to test exec.Cmd itself, but for code that merely invokes it, I think it makes more sense to use actual mocks.
2019-12-04 19:26:05 +00:00
require (
github.com/golang/mock v1.3.1
Replicate most of drone-helm's config
2019-12-09 17:56:02 +00:00
github.com/kelseyhightower/envconfig v1.4.0
Actual drone-invokable helm commands
2019-12-05 22:35:25 +00:00
github.com/stretchr/testify v1.4.0
Brush all the lint off this code I wrote in a haze
2019-12-09 18:52:41 +00:00
golang.org/x/lint v0.0.0-20191125180803-fdd1cda4f05f // indirect
golang.org/x/tools v0.0.0-20191206204035-259af5ff87bd // indirect
Very rough code that can `helm install` The recommended way to test code that uses exec.Cmd involves setting up a real exec.Cmd that invokes `go test` with additional arguments that fire off a specially-constructed test that behaves the way the mocked- out script would be expected to do. It's a sensible way to test exec.Cmd itself, but for code that merely invokes it, I think it makes more sense to use actual mocks.
2019-12-04 19:26:05 +00:00
)
Copy permalink