kubernetes/hack/after-build
Eric Paris ce6f2c8e4b Do not build genconversion and gendeepcopy twice
The hack/after-build/verify-* functions were using the hack/update-*
functions.  Which means that if you call hack/verify-* you will do the
build twice. Stop it.
2015-08-12 10:05:48 -04:00
..
README.md Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
update-generated-conversions.sh Add missing argument to function call and don't set GOPATH directly 2015-08-11 21:54:37 -07:00
update-generated-deep-copies.sh Add missing argument to function call and don't set GOPATH directly 2015-08-11 21:54:37 -07:00
update-generated-docs.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
update-swagger-spec.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
verify-generated-conversions.sh Do not build genconversion and gendeepcopy twice 2015-08-12 10:05:48 -04:00
verify-generated-deep-copies.sh Do not build genconversion and gendeepcopy twice 2015-08-12 10:05:48 -04:00
verify-generated-docs.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
verify-linkcheck.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
verify-swagger-spec.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00

These should be called only by a script (or a user) who knows that the binaries are built and correct. Normal users should just have the versions in ../ which should just always do a build.

Analytics