github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/hack/after-build
History
Chao Xu ae1293418b move experimental/v1 to experimental/v1alpha1; 
use "group/version" in many places where used to expect "version" only.
 		2015-09-24 15:32:11 -07: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 move experimental/v1 to experimental/v1alpha1; 2015-09-24 15:32:11 -07:00
update-generated-deep-copies.sh move experimental/v1 to experimental/v1alpha1; 2015-09-24 15:32:11 -07:00
update-generated-docs.sh Rework doc generation to simplify and centralize 2015-09-11 19:32:08 -04:00
update-swagger-spec.sh move experimental/v1 to experimental/v1alpha1; 2015-09-24 15:32:11 -07:00
verify-description.sh Moving Status object to a common package 2015-09-17 14:09:53 -07:00
verify-generated-conversions.sh Fix tooling for apis/experimental's new home 2015-09-11 16:06:10 -07:00
verify-generated-deep-copies.sh Fix tooling for apis/experimental's new home 2015-09-11 16:06:10 -07:00
verify-generated-docs.sh Rework doc generation to simplify and centralize 2015-09-11 19:32:08 -04:00
verify-generated-swagger-docs.sh Moving Status object to a common package 2015-09-17 14:09:53 -07: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

README.md

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