2018-11-13 08:06:22 +00:00
|
|
|
## Development Information
|
|
|
|
|
|
|
|
|
|
## How to build the multus-cni?
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
git clone https://github.com/intel/multus-cni.git
|
|
|
|
|
cd multus-cni
|
|
|
|
|
./build
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## How to run CI tests?
|
|
|
|
|
|
2019-09-20 01:57:49 +00:00
|
|
|
Multus has go unit tests (based on ginkgo framework).The following commands drive CI tests manually in your environment:
|
2018-11-13 08:06:22 +00:00
|
|
|
|
|
|
|
|
```
|
|
|
|
|
sudo ./test.sh
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## Logging Best Practices
|
|
|
|
|
|
2019-09-20 01:57:49 +00:00
|
|
|
Following are multus logging best practices:
|
2018-11-13 08:06:22 +00:00
|
|
|
|
2019-09-20 01:29:02 +00:00
|
|
|
* Add `logging.Debugf()` at the begining of functions
|
2018-11-13 08:06:22 +00:00
|
|
|
* In case of error handling, use `logging.Errorf()` with given error info
|
2019-09-20 01:29:02 +00:00
|
|
|
* `logging.Panicf()` only be used for critical errors (it should NOT normally be used)
|
2018-11-13 08:06:22 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
## CI Introduction
|
|
|
|
|
|
|
|
|
|
TBD
|
