|author||Matt Rutkowski <firstname.lastname@example.org>||Fri Jul 26 09:56:08 2019 -0500|
|committer||GitHub <email@example.com>||Fri Jul 26 09:56:08 2019 -0500|
remove general path exclusions in favor of granular file-level (#67) * Update scancode to include all Dockerfile variants * Update scancode to include all Dockerfile variants * Update scancode to include all Dockerfile variants * remove general path exclusions in favor of granular file-level
Shared utilities used across Apache OpenWhisk project repositories.
The following utilities are included in this repository (by subdirectory):
If you “push” code that follows all conventions, you will see the message:
Scanning files starting at [./mycodepath/]... All checks passed.
However, if you push code containing tabs, trailing whitespace or missing Apache License headers, your build will fail immediately with one of the following messages:
Scan detected 3 error(s) in 1 file(s): [./mycodepath/sourcecode.go]: 1: file does not include required license header. 18: line contains tabs. 27: line has trailing whitespaces.
To make sure this never happens to you, you can run the same tests on your local machine every time you commit changes.
$ git clone https://github.com/apache/incubator-openwhisk-utilities.git
# Invoke Python utility (works with either Python 2 or 3) $ python ./incubator-openwhisk-utilities/scancode/scanCode.py $ROOTDIR
It is worth adding a Git pre-commit hook to automatically run the checks before you can even type in a Git commit message. Here is a sample
$ cat /path/to/openwhisk/.git/hooks/pre-commit #!/usr/bin/env bash # determine openwhisk base directory root="$(git rev-parse --show-toplevel)" python /path/to/incubator-openwhisk-utilities/scancode/scanCode.py . --config $root/tools/ --gitignore $root/.gitignore
Note: A hook a locally installed, so if you check out the repository again, you will need to reinstall it.
If your project repo. is new or does not run scancode yet, you can choose to create a “pre-build” Bash script that can be included in your Travis CI integration that includes code similar to Step 1 and 2. You can invoke this script within the “.travis.yml” file early in your install or build scripts.
Report bugs, ask questions and request features here on GitHub.
You can also join our slack channel and chat with developers. To get access to our slack channel, request an invite here.