5 Commits (6320e41b4f81e23a24968565d74e3eb37aecd56b)

Author	SHA1	Message	Date
Thomas Liu	f4f04e2985	Include genyaml in update/verify generated docs scripts	2016-04-13 15:11:31 -07:00
Matt Liggett	08418a486d	Add debugging output to mungedocs when --verbose=true. ... Hope to understand why verify-generated-docs is failing on jenkins but not here.	2015-11-30 13:43:19 -08:00
feisky	13dce74adb	Gendocs for docs/admin/kube-*	2015-10-25 19:24:23 +08:00
Eric Paris	58d6b29e97	Rework doc generation to simplify and centralize ... Just do all doc generation in the hack::util::gen-docs instead of spread around. We also only track the generated docs in a single file for the whole tree.	2015-09-11 19:32:08 -04:00
Eric Paris	3b7c39656c	Split hack/{verify,update}-* files so we don't always go build ... Right now some of the hack/* tools use `go run` and build almost every time. There are some which expect you to have already run `go install`. And in all cases the pre-commit hook, which runs a full build wouldn't want to do either, since it just built! This creates a new hack/after-build/ directory and has the scripts which REQUIRE that the binary already be built. It doesn't test and complain. It just fails miserably. Users should not be in this directory. Users should just use hack/verify-* which will just do the build and then call the "after-build" version. The pre-commit hook or anything which KNOWS the binaries have been built can use the fast version.	2015-08-11 14:20:46 -04:00