summaryrefslogtreecommitdiff
path: root/build.sh
diff options
context:
space:
mode:
authorAndrey Kleshchev <andreykproductengine@lindenlab.com>2021-11-16 02:22:54 +0200
committerAndrey Kleshchev <andreykproductengine@lindenlab.com>2021-11-16 02:22:54 +0200
commit5ccdcf51a3b4cb46a8c9134636bc3bd5f2129f92 (patch)
treefd0dbaf5b47674beaf7abd159bfec5fcd1428766 /build.sh
parent3641541c6cc7f33f0e0dc2e1eb2cfdfcec23322b (diff)
parent9957c28ddc5e5c129af2db662da7d69f1509af65 (diff)
Merge branch master (DRTVWR-545) into DRTVWR-542-meshopt
Diffstat (limited to 'build.sh')
-rwxr-xr-xbuild.sh16
1 files changed, 16 insertions, 0 deletions
diff --git a/build.sh b/build.sh
index 50eb2916df..1b6dd17a4a 100755
--- a/build.sh
+++ b/build.sh
@@ -298,6 +298,22 @@ python_cmd "$helpers/codeticket.py" addinput "Viewer Channel" "${viewer_channel}
initialize_version # provided by buildscripts build.sh; sets version id
+begin_section "coding policy check"
+# On our TC Windows build hosts, the GitPython library underlying our
+# coding_policy_git.py script fails to run git for reasons we have not tried
+# to diagnose. Clearly git works fine on those hosts, or we would never get
+# this far. Running coding policy checks on one platform *should* suffice...
+if [[ "$arch" == "Darwin" ]]
+then
+ # install the git-hooks dependencies
+ pip install -r "$(native_path "$git_hooks_checkout/requirements.txt")" || \
+ fatal "pip install git-hooks failed"
+ # validate the branch we're about to build
+ python_cmd "$git_hooks_checkout/coding_policy_git.py" --all_files || \
+ fatal "coding policy check failed"
+fi
+end_section "coding policy check"
+
# Now run the build
succeeded=true
last_built_variant=