SonarQube analysis is working fine and we need help in getting sonar analysis in the bitbucket server.
In bitbucket, the webhook has been configured correctly and in SonarQube the pull request decoration settings are set (Configuration name, Project Key and Repository SLUG)
Need help in resolving the error “Pull request decoration did not happen. Failed to access Bitbucket Server, the repository or the pull request”
Screenshot of issue
Related
I am working on adding a proxy for Github Hosted maven repo. I have created the proxy and gave the remote storage url value as github url.
Anyone aware of how we can set up credentials for Nexus repo manager to talk to Github Repo. I am new to this stuff, so any help would be highly appreciated. I am guessing we might need to setup some generic user in github and created authentication token and use those for nexus to talk to Github?
Thanks in advance.
So I currently am trying to get artifacts from repo.osegeo.org, which is a Nexus V3. I am having issues getting the artifacts to populate into my virtual repo that i created which holds the remote osegeo repo, libs release, libs snapshot and also my local repos. I have tried following the work around that is stated in this link below:
https://community.sonatype.com/t/maven-nexus-v3-remote-repository-integration-with-artifactory/2149
But I still have trouble actually getting the artifacts in my repo. Any ideas on what to do?
I suggest checking the following:
Connectivity - Is Artifactory able to reach the Nexus repository and vice versa?
The URL which is configured and if it is configured correctly.
Enable Bypass HEAD requests on the remote repository - Nexus can block HEAD requests and by default, Artifactory will create HEAD requests first before the GET requests to check if the artifact exists before attempting to resolve it.
If the Nexus repository requires authentication - Do not forget to put username and password under the advanced tab.
If there is also a reverse proxy in front of Nexus, you can try to bypass it and check if this works, if it does, the problem is probably the RP.
Check if the Maven client is configured correctly to work against the virtual repository (You didn't mention if you are able to publish or fetch from the local repository).
Does the Sonarqube Auth Bitbucket plugin work with Bitbucket Server or only Bitbucket Cloud?
https://github.com/SonarQubeCommunity/sonar-auth-bitbucket
A pull request has been submitted in order to be able to configure the bitbucket server URL : https://github.com/SonarQubeCommunity/sonar-auth-bitbucket/pull/9
Feel free to test it and to provide feedbacks !
We have a teamcity local instance running and a bitbucket cloud instance.
I have configured the connection correctly and I can see that teamcity has accessed via the oath several times.
In teamcity it allows me to login and says to refresh after the successful login but it just cycles through the login again.
No clue what is wrong
#LukeP helped me with the first issue , now theres a second]2
Any ideas how to resolve this?
I added a proxy repository in nexus. When I update now in Routing, it failed. The repo url I added is https://raw.githubusercontent.com/dianping/cat/mvn-repo
I can access this url
https://raw.githubusercontent.com/dianping/cat/mvn-repo/org/unidal/maven/plugins/codegen/2.3.2/codegen-2.3.2.pom
I can't access this url
https://raw.githubusercontent.com/dianping/cat/mvn-repo
response 400: Invalid request
So. It's the repo server block nexus from update.
If I don't use mirror in maven setting, Maven update will work right.
Meanwhile, when I use nexus public repositores group as my mirror(I also added proxy repo to public repositories group), It just report Failure to find org.unidal.maven.plugins:codegen-maven-plugin:jar:2.3.2
in http://172.xxx/nexus/content/groups/public
How can I solve this problem?
And I guess the maven resolve flow is like:
maven resolve a dependency
find the dependency in local
find in repo manager
find in proxy repo.
As the full url like https://raw.githubusercontent.com/dianping/cat/mvn-repo/org/unidal/maven/plugins/codegen/2.3.2/codegen-2.3.2.pom can be access, repo manager could fetch the specific pom url, if my guess is right.
I wonder: Unlike maven central,which you can access its index or called file tree, this cat.repo you can only access its file but not its directory. So what's the diffenrence in maven? How to handle this?
EDIT
Because I've successed update not using <mirrorOf>*</mirrorOf>. My local repository already download these missing plugins in Nexus. So I follow the tips in Maven not using the local repo, and that missing plugin does not cause error again, but another artifact not found in nexus again.
I also do as maven missing artifact shows, by
Deleting maven-metadata*.xml and _*.repositories inside local
Still not working.
The remote is returning HTTP code 400 (invalid request) for request to "/".
Nexus does HEAD and GET requests to the root URL to determine if the remote is reachable, and in good health. This response code is causing Nexus to think the remote is not working.
To work around this, go to the proxy repository's configuration tab and set "auto-blocking enabled" to "false".
You can also get this failure if you are doing an http request to a server that only allows https.