Nexus Download File From Raw Repository
Tyler Janicke
Try checking the request.log to see if the 403 is actually coming from Nexus Repo (it may be coming from something in between jenkins and nexus). If it is coming from Nexus Repo the user ID associated with the request will be printed in the third column. Make sure that user has write access to the repository.
I was struggling about this problem last two days, finally the solution was to delete .npmrc file from root (user) directory.When npm tried to login, it used the creds inside this file and ignore your pass login.
I thought there was no way of deleting artifacts from hosted repositories via web interface. Now I see that in the "Browse storage" section I can delete the artifact directory, which is the the recommended way I guess.
In this article, I intend to share my experience of migrating from Nexus docker registry to Harbor and the steps involved. Additionally, I will compare some of the most useful features of Harbor to those of Nexus and provide reasons why you should consider using it:
The old one should actually still be there. But we moved with our office to a new location and therefore the server was not reachable.
Anyway, you should use the new repository. Sorry for the inconvenience.
I cant seem to work this out (or maybe its just late!) - I installed Nexus and disabled anonymous access as I intend to proxy nexus on the web. It makes sense that there should be some manner to authenticate against the nexus repository, but I cant find anywhere to configure this.
Edit: It seems to work. The Nexus goes into the Gradle Central Plugin Repository, but only retrieves the POM files, as there is only pom files. After running gradle I have checked that the Nexus Gradle proxy repository does contain various plugins, but only the POM files and no JAR files.
Is the URL to Gradle Central Plugin Repository I am using correct?
With the legacy plugin application one could specify the repository for these plugins in the buildscript section. However that does not work either, it still goes to gradle central plugin repository.
When using the Gradle Plugin Portal this is more or less transparent as the Plugin Portal redirects to JCenter (or its proxy) which forwards to Maven Central if some artifact is not found in the own repository. But at least the plugin marker artifacts for most of the plugins should actually live inside Gradle Plugin Portal, as otherwise the respecitve plugin is also not discoverable via the search on plugins.gradle.org.
Non-resolvable import POM: Could not transfer artifact org.camunda.bpm:camunda-bom:pom:7.15.0-ee from/to camunda-bpm-nexus-ee ( -bpm-ee/): authentication failed for -bpm-ee/org/camunda/bpm/camunda-bom/7.15.0-ee/camunda-bom-7.15.0-ee.pom, status: 401 Unauthorized
760c119bf3