Files
kubernetes/hack
hasheddan 89bfeb5fb4 Update verify-no-vendor-cycles to use dependencycheck
verify-no-vendor-cycles currently routinely takes 3-4 minutes to run due
to the way that it checks for cyclical imports in vendored packages.
Moving to using the new dependencycheck tool makes this test much faster.

Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
2020-08-01 08:11:05 -05:00
..
2020-07-06 10:38:39 -04:00
2020-07-01 10:50:28 -04:00
2019-02-22 10:00:10 -08:00
2019-11-03 19:36:59 -05:00
2019-01-22 08:39:55 +08:00
2019-01-22 08:39:55 +08:00
2020-01-29 09:27:51 +09:00
2020-07-06 10:39:56 -07:00
2020-01-16 10:12:18 +08:00
2020-01-28 09:27:40 +09:00
2020-05-29 09:56:00 +08:00

Kubernetes hack GuideLines

This document describes how you can use the scripts from hack directory and gives a brief introduction and explanation of these scripts.

Overview

The hack directory contains many scripts that ensure continuous development of kubernetes, enhance the robustness of the code, improve development efficiency, etc. The explanations and descriptions of these scripts are helpful for contributors. For details, refer to the following guidelines.

Key scripts

  • verify-all.sh: This script is a vestigial redirection, Please do not add "real" logic. It is equivalent to make verify.
  • update-all.sh: This script is a vestigial redirection, Please do not add "real" logic. The true target of this makerule is hack/make-rules/update.sh.It is equivalent to make update.

Attention

Note that all scripts must be run from the Kubernetes root directory. We should run hack/verify-all.sh before submitting a PR and if anything fails run hack/update-all.sh.