Skip to content
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

[Bug][Sonarqube] No option to add scope config even though documentation suggests #7931

Closed
2 of 3 tasks
sanjchhoker opened this issue Aug 21, 2024 · 7 comments
Closed
2 of 3 tasks
Assignees
Labels
component/config-ui This issue or PR relates to config-ui severity/p1 This bug affects functionality or significantly affect ux type/bug This issue is a bug

Comments

@sanjchhoker
Copy link

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

Add sonarqube connection and add data scope to the connection - I can see data scopes coming through but cannot see scope config option.
It’s all just N/A
IMG_6953

What do you expect to happen

Expect to see option to add scope config and only then we can get DORA metrics

How to reproduce

Add sonarqube connection and the add data scope.

Anything else

No response

Version

v1.0.0

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@sanjchhoker sanjchhoker added the type/bug This issue is a bug label Aug 21, 2024
Copy link

dosubot bot commented Aug 21, 2024

Hey @sanjchhoker! I'm here to help you out with any bugs, questions, or contributions you have in mind. I'm a bot, but don't worry, I'll do my best to assist you while we wait for a human maintainer to join the conversation.

The issue you're encountering is likely due to the ScopeConfig method returning nil, which means there is no scope configuration available for SonarQube. This is a known limitation mentioned in the documentation:

func (p Sonarqube) ScopeConfig() dal.Tabler {
    return nil
}

To resolve this, you would need to ensure that the pluginConfig.scopeConfig setting is enabled in the code. This setting controls whether the scope config option appears in the UI:

{pluginConfig.scopeConfig && (
  <IconButton
    icon={<LinkOutlined />}
    helptip="Associate Scope Config"
    size="small"
    type="link"
    onClick={() => {
      setType('associate');
    }}
  />
)}

If pluginConfig.scopeConfig is not enabled, the scope config option will not be displayed [1][2].

To continue talking to Dosu, mention @dosu.

@sanjchhoker
Copy link
Author

fyi I am using Sonarqube enterprise v10.6

@dosubot dosubot bot added component/config-ui This issue or PR relates to config-ui severity/p1 This bug affects functionality or significantly affect ux labels Aug 21, 2024
@klesh
Copy link
Contributor

klesh commented Sep 6, 2024

What document were you referring to?
I can clearly see that Sonarqube data source doesn't have any scope config: https://devlake.apache.org/docs/Configuration/SonarQube#step-3---adding-transformation-rules-optional

@klesh klesh added severity/p2 This bug doesn’t affect the functionality or isn’t evident and removed severity/p1 This bug affects functionality or significantly affect ux labels Sep 6, 2024
@sanjchhoker
Copy link
Author

@klesh
Copy link
Contributor

klesh commented Sep 9, 2024

@sanjchhoker I see.
Sorry for missing the point, my brain somehow filtered the section completely for me. 😂
Will update the doc soon.

@klesh klesh added severity/p1 This bug affects functionality or significantly affect ux and removed severity/p2 This bug doesn’t affect the functionality or isn’t evident labels Sep 9, 2024
@Startrekzky
Copy link
Contributor

Hi @sanjchhoker , the docs have been updated by: apache/incubator-devlake-website#787

You'll see the latest doc after it gets merged.

@Startrekzky
Copy link
Contributor

The updated sonarqube doc: https://devlake.apache.org/docs/Configuration/SonarQube/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/config-ui This issue or PR relates to config-ui severity/p1 This bug affects functionality or significantly affect ux type/bug This issue is a bug
Projects
None yet
Development

No branches or pull requests

3 participants