Files
kubernetes/hack
Patrick Ohly 9ff8bdbd25 ginkgo: disable color escape sequences by default when not connected to a terminal
This applies to all jobs using hack/ginkgo-e2e.sh. This is done because
Spyglass does not render the escape sequences, making test output harder to
read.

It is done here because then we don't need to set GINKGO_NO_COLOR in all the
different Prow job configs.
2022-08-02 14:19:10 +02:00
..
2021-02-28 15:17:29 -08:00
2022-07-26 13:14:05 -04:00
2022-02-14 10:55:35 -07:00
2022-06-21 17:33:46 +08:00
2022-06-26 09:21:05 +05:30
2022-07-08 10:46:11 +08:00
2022-05-31 08:07:37 +02:00
2022-03-02 10:04:11 -05:00
2022-06-24 17:58:34 +00:00
2020-11-10 14:17:17 -08:00
2021-03-07 12:51:33 -08:00
2020-09-03 23:29:07 +00: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.