-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCANNPM-5 Update CI tasks #127
Conversation
02f41f3
to
1d8ea40
Compare
//TODO: return to true once SC has the new provisioning mechanism in place | ||
return false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was to force the scanner to run the scanner-cli for SC. this needs to be reverted before we merge)
@@ -87,7 +87,7 @@ describe('java', () => { | |||
...MOCKED_PROPERTIES, | |||
[ScannerProperty.SonarScannerInternalIsSonarCloud]: 'true', | |||
}), | |||
).toBe(true); | |||
).toBe(false); // TODO: return to true once SC has the new provisioning mechanism in place |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this also need to be reverted, just modified to test the CI is passing
.npmignore
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I needed to add this so that npm publish would include the build
directory. The other alternative was to NOT .gitignore the build directory, but the files don't conform to the prettier settings because they are minified.
I am open to a better solution here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think if we set files: ["build/**"]
in the package.json
, then the build
folder will automatically be included in the released package (even if it's gitignored)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://docs.npmjs.com/cli/v8/commands/npm-publish#files-included-in-package
I would say we need to only release build
folder and the cli src\bin\sonar-scanner
. All the rest can be ignored.
1d8ea40
to
561be42
Compare
a0f288d
to
e195ebf
Compare
e195ebf
to
771a56b
Compare
// Skip if not a .js file | ||
if (!fileName.endsWith('.js')) { | ||
continue; | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added back for the *.d.ts
files
Quality Gate failedFailed conditions See analysis details on SonarCloud Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
# Conflicts: # src/properties.ts # test/unit/config.test.js
Co-authored-by: Victor <victor.diez@sonarsource.com>
Co-authored-by: Victor <victor.diez@sonarsource.com>
Co-authored-by: Victor <victor.diez@sonarsource.com>
No description provided.