Scan each contained Typescript package when the scan of the whole source repository failed #244
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JohT
force-pushed
the
feature/scan-each-package-when-repo-scan-failed
branch
from
61ac659 to
dbd8566
Compare
JohT
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🚀 Feature
Scan each contained package when whole repo scan failed:
There are situations where the scan of a source repository might fail (e.g. running out of heap memory) or lead to an empty result (e.g. configuration issues). Previously, this lead to a failing scan and therefore no (simple) way to proceed with the analysis.
Now, a second try will be started where every contained package is scanned individually. This can solve the problem in many cases since the scans are then smaller and independent of the root configuration.
One drawback of that is that the
TS:Scannode can't be used for detecting the name of the repository since it will then have the same name as the package. There are then also more scans and they can then also include test, example and tutorial packages that might otherwise be skipped.