machine/CI user token


(Mattmoskwa) #1

Is there a way to generate a token that can be used by the CI that’s not tied to a specific account? Our use case is that we are using the SonarQube Scanner plugin for Jenkins and connecting it to SonarCloud. This works fine as long as we use the same token for each project, but currently that token is attached to a single user account, which means that user has to create each project individually. This is becoming time-consuming, and we would like other users to be able to create their own projects in sonarcloud for use with Jenkins.

(Fabrice Bellingard) #2

I see your problem, and currently there is no solution other than creating a dedicated “bot” account for which you will generate a token.

(Mattmoskwa) #3

Is there anything the pipeline? Can I make a feature request?

(Fabrice Bellingard) #4

Before answering further, can you clarify:

  • where your sources are hosted
  • what type of code you want to analyze

(Mattmoskwa) #5

We host our source code on Github. We have a very large codebase across dozens of repos that includes java, android, kotlin, groovy, apex, javascript, python, and probably a few more.

(Fabrice Bellingard) #6

OK, except for Java (and Groovy that is not supported), you might want to try the Automatic Analysis feature we are developing. This is the future, and this removes the need for you to manage tokens. I’d be happy to hear what you think about this!