Shared utilities used across Apache OpenWhisk project repositories.

The following utilities are included in this repository (by subdirectory):

• scancode - Configurable code scanning utility that performs file and line-level checks on all files (exclusions permitted) on a provided path. It is intended for Git commit hooks and continuous integration (CI) builds to enforce certain coding conventions.

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.

1. Clone the OpenWhisk utilities project:

$ git clone https://github.com/apache/openwhisk-utilities.git

2. Run the scancode utility against the root directory of your project or subdirectory where your code changes live:

# Invoke Python utility (works with either Python 2 or 3)
$ python ./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 pre-commit file:

$ cat /path/to/openwhisk/.git/hooks/pre-commit
#!/usr/bin/env bash

# -- Code scanning --
# See https://github.com/apache/openwhisk-utilities
# determine openwhisk base directory
root="$(git rev-parse --show-toplevel)"
scancode_path="/path/to/openwhisk-utilities/scancode"
python $scancode_path/scanCode.py --config $scancode_path/ASF-Release.cfg --gitignore $root/.gitignore $root

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.