#!/bin/bash

# Copyright 2015 Google Inc. All rights reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

FILES=$(go vet k8s.io/heapster/... 2>&1)
if [[ ! -z "$FILES" ]]; then
echo -e "Run go fix on the following files:\n $FILES"
  exit 1
fi

#!/bin/bash

# Copyright 2015 Google Inc. All rights reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

set -o errexit
set -o pipefail

# Filter silly "exit status 1" lines and send main output to stdout.
#
# This is tricky - pipefail means any non-zero exit in a pipeline is reported,
# and errexit exits on error.  Turning that into an || expression blocks the
# errexit.  But $? is still not useful because grep will return an error when it
# receives no input, which is exactly what go vet produces on success.  In
# short, if go vet fails (produces output), grep will succeed, but if go vet
# succeeds (produces no output) grep will fail.  Then we just look at
# PIPESTATUS[0] which is go's exit code.
rc=0
go vet ./... 2>&1 | grep -v "^exit status " || rc=${PIPESTATUS[0]}
exit "${rc}"

Improve go vet output by reusing kubernetes code
Improve go vet output by reusing kubernetes code

This is a simplified version of the code in kubernetes that runs go vet.
Advantages over ours:

* Prints the errors instead of telling you to find them out for yourself
* Doesn't tell you to run `go fix` (fix only fixes usage of old apis)
* Doesn't hard-code k8s.io/heapster unnecessarily
