Rename build script to avoid conflict with bazel
It's difficult to include this repository using bazel, because the file named "build" conflicts with new_go_repository generation on case-insensitive filesystems (ref https://github.com/bazelbuild/rules_go/issues/234). This change renames the file to something that doesn't conflict, and also renames the test script for consistency.
This commit is contained in:
@@ -40,7 +40,7 @@ This is a rough outline of how to prepare a contribution:
|
||||
- If you changed code:
|
||||
- add automated tests to cover your changes, using the [Ginkgo](http://onsi.github.io/ginkgo/) & [Gomega](http://onsi.github.io/gomega/) style
|
||||
- if the package did not previously have any test coverage, add it to the list
|
||||
of `TESTABLE` packages in the `test` script.
|
||||
of `TESTABLE` packages in the `test.sh` script.
|
||||
- run the full test script and ensure it passes
|
||||
- Make sure any new code files have a license header (this is now enforced by automated tests)
|
||||
- Submit a pull request to the original repository.
|
||||
@@ -59,7 +59,7 @@ sudo su
|
||||
cd /go/src/github.com/containernetworking/cni
|
||||
|
||||
# to run the full test suite
|
||||
./test
|
||||
./test.sh
|
||||
|
||||
# to focus on a particular test suite
|
||||
cd plugins/main/loopback
|
||||
|
||||
Reference in New Issue
Block a user