The default builder in Jenkins is '/bin/sh -ex'. Because of this lint
jobs are failing that we assume won't as everywhere else we've used
/bin/bash and explitily set options when needed.
Explicitly setting these jobs to use /bin/bash should keep Jenkins from
failing builds without reporting the lint results.
Change-Id: Ibe6cad979d6dcf30e7991873c9ac446ae3bf3a8b
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
name: lint-init
builders:
- shell: |
+ #!/bin/bash
# Ensure we start with a clean environment
rm -f bash-violation.log python-violation.log yaml-violation.log violation.log
git --no-pager diff --diff-filter=MCRAT --name-only HEAD^1 > modified_files
name: lint-report
builders:
- shell: |
+ #!/bin/bash
if [[ -s violation.log ]]; then
echo "Reporting lint result..."
msg="Found syntax error and/or coding style violation(s) in the files modified by your patchset."
name: lint-bash-code
builders:
- shell: |
+ #!/bin/bash
echo "Checking bash code..."
for f in $(egrep '\.sh$' modified_files)
do
name: lint-python-code
builders:
- shell: |
+ #!/bin/bash
# Install python package
sudo pip install "flake8==2.6.2"
name: lint-yaml-code
builders:
- shell: |
+ #!/bin/bash
# sudo Install python packages
sudo pip install "yamllint==1.8.2"