This repository has been archived by the owner on Aug 21, 2023. It is now read-only.
Fix tslint whitespace issue in Jenkins env #324
Merged
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.
Overview
tslint throws a "missing whitespace" error in the jsdoc comment of image-export.service.ts, but only in the jenkins environment.
This issue is tracked here: palantir/tslint#3251 and a scan through the comments indicates a general 🤷 that its caused by some magic combination of node + npm+ yarn + typescript + tslint + tsutils and that updating to yarn 1.2+ fixes it. I attempted this upgrade in place while SSHed into Jenkins but had no luck. I might have done something wrong getting node_modules cleaned out though.
So, for now I just removed the
whitespace.check-separator
in tslint as a workaround. I'm hopeful that a separate task to update yarn in the docker container on Jenkins would address the deeper issue.Edit: first attempting a yarn version upgrade on fresh Jenkins build.Created #325 to more thoroughly fix the issue.
Testing Instructions
Jenkins should now build successfully.
Checklist
yarn run serve
clean?yarn run build:prod
clean?yarn run lint
clean?