-
Notifications
You must be signed in to change notification settings - Fork 693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use make #3007
use make #3007
Conversation
Adds the following human-facing targets: - merge: builds and installs the merge binary - config: creates a merged config using the merge binary - test: tests the merged config using go test - peribolos: clones a local copy of kubernetes/test-infra and installs the peribolos binary - deploy: runs periobolos to deploy the merged config if tests pass - clean: remove all intermediary configs and binaries Overrideable env vars: - GITHUB_TOKEN_PATH: value for --github-token-path passed to peribolos - TEST_INFRA_PATH: set to location of a pre-existing clone of kubernetes/test-infra to avoid cloning a temporary copy One way this differs from bazel is that we're not necessarily getting the latest version of test-infra each time we run `make deploy` but I don't foresee peribolos changing that frequently, and a `make clean` is enough to get us back to "latest" state.
The verify-all.sh script ends up calling //hack:verify-all as defined in kubernetes/repo-infra. Two of these checks are bazel-specific and can be removed / ignored for porting: - verify-bazel - verify-deps The other two make sense without bazel, so copy them over: - verify-gofmt.sh (and update-gofmt) - verify-boilerplate.sh Then add a hack/verify.sh script (copied from kubernetes/k8s.io) that calls all verify scripts (excluding verify-all.sh, to allow the bazel-based tests to still run/pass) Then add a verify target to the Makefile
@@ -1,4 +1,4 @@ | |||
#!/usr/bin/env python | |||
#!/usr/bin/env python3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A note here: I didn't make any of these edits myself. I merely downloaded the latest copy of the script from kubernetes/repo-infra
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cblecker, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
I grew tired of recompiling protobuf to see if our YAML-based config was sorted
Adds the following human-facing targets:
merge
: builds and installs the merge binaryconfig
: creates a merged config using the merge binarytest
: tests the merged config using go testverify
: runs hack/verify.shperibolos
: clones a local copy of kubernetes/test-infra and installsthe peribolos binary
deploy
: runs periobolos to deploy the merged config if tests passclean
: remove all intermediary configs and binariesOverrideable env vars:
GITHUB_TOKEN_PATH
: value for--github-token-path
passed toperibolos
TEST_INFRA_PATH
: set to location of a pre-existing clone ofkubernetes/test-infra to avoid cloning a temporary copy
One way this differs from bazel is that we're not necessarily getting
the latest version of test-infra each time we run
make deploy
but Idon't foresee peribolos changing that frequently, and a
make clean
isenough to get us back to "latest" state.