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

Anonymous analysis #13

Closed
Thorn1089 opened this issue Mar 5, 2018 · 1 comment
Closed

Anonymous analysis #13

Thorn1089 opened this issue Mar 5, 2018 · 1 comment

Comments

@Thorn1089
Copy link

The login parameter is required on the resource definition. However my Sonar instance is on a private network and doesn't require a username or access token to push analysis results to.

Leaving the login field blank in my pipeline YAML doesn't seem to work.

How can I use this resource with an open Sonarqube instance?

@headcr4sh
Copy link
Member

You are right, the login parameter is mandatory.
I assume that even when running SonarQube on a private network it is a good idea to create a different user for the CI/CD system. One advantage e.g. is that you can easily distinguish between analysis-runs that have been triggered by the CI/CD system and those triggered by another user.

assets/common.sh would need to be patched if an open SonarQube instance is indeed a valid use-case. I will probably not find the time to provide a patch myself in the next few days-- but I'll gladly except one if it doesn't break anyhing else. ;-)

@headcr4sh headcr4sh added this to the 0.3.0 milestone Mar 7, 2018
@headcr4sh headcr4sh modified the milestones: 0.3.0, 0.4.0 Mar 28, 2018
@headcr4sh headcr4sh modified the milestones: 0.4.0, 0.5.0 May 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants