96b88e286e
Jenkins doesn't do a very good job with identifying what has been changed. While it has a syntax to defined patterns, it compares the current build with the previous build (in case of git-verify it can be a totally different branch) instead of checking the HEAD commit. This patch introduces shell scripts to do this better: * It doesn't depend on Jenkins any more * It can be executed locally * It can detect web changes properly (see the relation change as an example). Change-Id: I9d37775e3818c08c4aa96ffb78f84d57f28a2c95
15 lines
338 B
Bash
Executable File
15 lines
338 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Copyright (C) 2022 Storj Labs, Inc.
|
|
# See LICENSE for copying information.
|
|
|
|
cd "$(dirname "${BASH_SOURCE[0]}")"
|
|
set -euxo pipefail
|
|
|
|
npm install --prefer-offline --no-audit --logleve verbose
|
|
touch ./node_modules/go.mod # prevent Go from scanning this dir
|
|
npm run build
|
|
|
|
npm run lint-ci
|
|
npm audit || true
|
|
npm run test
|