"make push-multiarch" matched both push-multiarch and push-%. This seems to be none-deterministic and in at least one repo (external-provisioner), make picked the wildcard rule which then failed because there is no "multiarch" command. This ambiguity gets resolved by instantiating the wildcard rules only for existing commands. The advantage also is that "make push-no-such-command" will fail with an obvious "No rule to make target 'push-no-such-command'" instead of attempting to build the command.
Name |
Last commit
|
Last update |
---|---|---|
.prow.sh | Loading commit data... | |
CONTRIBUTING.md | Loading commit data... | |
LICENSE | Loading commit data... | |
OWNERS | Loading commit data... | |
README.md | Loading commit data... | |
RELEASE.md | Loading commit data... | |
SECURITY_CONTACTS | Loading commit data... | |
SIDECAR_RELEASE_PROCESS.md | Loading commit data... | |
build.make | Loading commit data... | |
cloudbuild.sh | Loading commit data... | |
cloudbuild.yaml | Loading commit data... | |
code-of-conduct.md | Loading commit data... | |
filter-junit.go | Loading commit data... | |
go-get-kubernetes.sh | Loading commit data... | |
prow.sh | Loading commit data... | |
travis.yml | Loading commit data... | |
update-vendor.sh | Loading commit data... | |
util.sh | Loading commit data... | |
verify-go-version.sh | Loading commit data... | |
verify-shellcheck.sh | Loading commit data... | |
verify-subtree.sh | Loading commit data... | |
verify-vendor.sh | Loading commit data... |