Build Tooling: Use "full" npm install
for Build Artifacts Travis task
#16166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: #16157
This pull request seeks to change to the install step for the Travis "Build artifacts" task to use
npm install
instead ofnpm ci
. The purpose of this task is to capture local changes occurring as the result ofnpm install
(ornpm run docs:build
), typically in the form of an unsyncedpackage-lock.json
file. Historically, this test has often resulted in false negatives, due to issues withnpm ci
described in #16157.Testing Instructions:
These changes impact only Travis configuration. The "Build artifacts" test case in particular should continue to pass. If necessary, we can demonstrate it capturing intended errors with a temporary commit to the branch.