Skip to content

Commit 22ee7af

Browse files
skinny85Curtis Eppel
authored and
Curtis Eppel
committed
build: skip compatibility check for Gitpod (aws#9315)
There is no point in doing the compatibility check when spinning up a new Gitpod workspace, so add an option to build.sh to skip it, and use it for the Gitpod build. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
1 parent 7b29a2c commit 22ee7af

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed

.gitpod.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
image: jsii/superchain
22
tasks:
3-
- init: yarn build --skip-test --no-bail --skip-prereqs
3+
- init: yarn build --skip-test --no-bail --skip-prereqs --skip-compat
44

55
vscode:
66
extensions:

build.sh

+7-1
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ set -euo pipefail
44
bail="--bail"
55
runtarget="build+test"
66
check_prereqs="true"
7+
check_compat="true"
78
while [[ "${1:-}" != "" ]]; do
89
case $1 in
910
-h|--help)
@@ -22,6 +23,9 @@ while [[ "${1:-}" != "" ]]; do
2223
--skip-prereqs)
2324
check_prereqs="false"
2425
;;
26+
--skip-compat)
27+
check_compat="false"
28+
;;
2529
*)
2630
echo "Unrecognized parameter: $1"
2731
exit 1
@@ -70,6 +74,8 @@ echo "==========================================================================
7074
echo "building..."
7175
time lerna run $bail --stream $runtarget || fail
7276

73-
/bin/bash scripts/check-api-compatibility.sh
77+
if [ "$check_compat" == "true" ]; then
78+
/bin/bash scripts/check-api-compatibility.sh
79+
fi
7480

7581
touch $BUILD_INDICATOR

0 commit comments

Comments
 (0)