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 !
Related
Is there a possibility to authenticate to GitHub as an GitHub App and publish packages as the GitHub App identity from Jenkins? Personal access tokens can be used but they use an identity of a separate user.
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
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.
As part of our TFS build I'm trying to push the latest package from our build pipeline to our Octopus Deploy instance. However I'm getting the following error.
I'm using a script task to execute the following octo push command.
octo push --package=mypackage.nupkg --overwrite-mode=OverwriteExisting --server=https://mycompany.octopus.app --user=myname#mycompany.com --pass=mypassword --debug --LogLevel=debug
Any ideas what's causing the error and how do I fix it?
It looks attempting to log in to the Octopus server using a username and password, but your instance isn't configured to accept that authentication type.
Is this pipeline pushing to an Octopus Cloud instance? If so, your authentication is via OctopusID, an external auth provider, rather than a username/password account on the Octopus instance itself.
As a general rule, using an API key is the recommended approach here, rather than username/password authentication.
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?