-
Notifications
You must be signed in to change notification settings - Fork 180
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
JS-597 Remove 'sonar-runtime' from codebase #5163
Conversation
const config = extendRuleConfig( | ||
[{ enum: SONAR_RUNTIME, title: SONAR_CONTEXT }], | ||
// @ts-ignore | ||
{ sonarKey: 'some-rule', meta: {}, schema: [{ title: SONAR_CONTEXT }] }, |
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 existing schema was and is not valid. I'll remove it soon, but for now just ignore it. During runtime it seems to be fine.
@@ -119,6 +118,9 @@ void test() { | |||
) | |||
) | |||
).isEmpty(); | |||
assertThat( | |||
buildResult.getLogsLines(l -> l.matches(".*INFO: Work dir received: .*[/|\\\\].scannerwork$")) |
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.
thats specific to windows? Is this test also ran on a sane platform?
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.
its are also run on windows, yes. when checking logs for paths or validating paths in general, windows may fail if u always use forward slashes
|
JS-597
Part of