You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 7, 2021. It is now read-only.
When running under maven (and maybe other runners) we can access sonar.links.scm.
This should allow us to calculate the baseurl, repository and project automatically (if the setting is correctly configured)
The text was updated successfully, but these errors were encountered:
@t-8ch
We run the sonar analysis on pull-requests from jenkins. To trigger the build we are using the stashPullRequestBuilderPlugin which have already the credentials settings.
The StashNotifier-plugin also have the stash credentials.
Im thinking about wrapping the execution of sonar goal into some jenkins plugin or adding the custom property to maven goal for loading some jenkins settings.
Which solution do you prefer, so I can try contribute with poc.
@gauee
I would prefer to keep any notion of the execution environment out of the sonar-stash plugin.
If you create a dedicated plugin this is completely fine (although I think it is probably overkill), but then the plugin would not really care, right?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When running under maven (and maybe other runners) we can access
sonar.links.scm
.This should allow us to calculate the baseurl, repository and project automatically (if the setting is correctly configured)
The text was updated successfully, but these errors were encountered: