I have one hosted nexus repository that proxy in different region another nexus machine, right now both are on same version. Does one nexus server upgrade impact on proxy repository.? both should be on same version and required to upgrade both on same time ??
Related
We are planning to migrate from nexus2 to nexus3. I intend to select only the proxy repos that are currently active in nexus2 and move them to nexus 3. Moreover, I think copy of proxy repo configuration would suffice, as the artifacts will anyways get downloaded in nexus 3 storage, when the build happens. Is it possible to copy only the configs of required proxy repos via upgrade wizard ? or is there any other way to achieve this?
Thanks!
i have 2 Artifactory server and have configured ubuntu repos.
One off the artifactorys goes to internet to ubuntu and the other
artifactory connects to the artifactory with internet access.
I have the following problem. From my local artifactory i get always the error 404.
I cant fetch the metafile (Packages) from the ubuntu repo.
But if i reconfigure my remote repo and set --> store artifacts locally all seems fine.
I want store the artifacts locally. My local artifactory should ask the artifactory with internet access and should get all files from the remote artifactory.
Have anyone a idea how to solve my problem?
best regards
I assume you are trying to set up a smart remote repository with Artifactory. Refer to this wiki and set up the smart remote repository, basically, you should be adding the URL in your local Artifactory's remote repository as http://ARTIFACTORY_URL/ubuntu-remote/ and make sure the "store artifacts locally"is checked so that this remote repository can able to index the artifacts.
I have set up Artifactory OSS Version 6.9.1 on an AWS instance behind an ELB and have been successfully deploying builds to it from GitLab CI/CD. I am now trying to set up a local Artifactory OSS Version 6.10.0 on my laptop so that I can develop builds locally before sharing with the team.
My local artifactory connects perfectly to JCentre and I can browse that repository.
My gradle build will happily connect to the AWS hosted artifactory at http://{URL}/artifactory and resolve my dependencies.
When I connect a remote repository with http://"{URL}/artifactory I get a 500 Internal Error message on Test. If I take off the /artifactory it says it has connected successfully but when I try to browse the remote repo it is empty.
I read Connect one Artifactory to another Artifactory and followed the instructions to edit the json configuration and make the remote repository a smart repository here https://www.jfrog.com/confluence/display/RTF/Smart+Remote+Repositories.
It now has the smart repository image but still cannot be browsed.
Gradle still cannot resolve dependencies with the local artifactory using the remote-repo name.
As stated in the Smart Remote Repository documentation, you should configure the remote repository URL with the following structure:
http://ARTIFACTORY_URL/api/package-type/repository-key
So if you have a Gradle repository named "gradle-test", the URL should be:
http://ARTIFACTORY_URL/api/gradle/gradle-test
Hope this helps.
In the end it turned out to be ridiculously simple. When setting up the remote repository the key needs to be in the url as well as the key field.
So for a repo with a repository key 'fractal' the connection URL is counter-intuitively http:///artifactory/fractal
I'm trying to proxy https://flywaydb.org/repo using Nexus Repository OSS v2.13.0 because we rely on flyway-sbt sbt plugin.
I can download the plugin fine if I add
resolvers += "Flyway" at "https://flywaydb.org/repo"
to plugins.sbt
But we want to proxy the artefacts using a local Nexus repository because we don't want our builds to depend on a server that is outside our control.
However when I add the server to Nexus (using Maven2 as provider and format) Nexus is unable to proxy artefacts and I get following error in logs:
[proxy-3-thread-5] admin org.sonatype.nexus.proxy.maven.maven2.M2Repository - Remote peer of proxy repository "flywaydb.org" [id=flywaydb.org] threw a org.sonatype.nexus.proxy.ItemNotFoundException exception. Auto-blocking this repository to prevent further connection-leaks and known-to-fail outbound connections until administrator fixes the problems, or Nexus detects remote repository as healthy. - Cause(s): Remote peer of repository M2Repository(id=flywaydb.org) detected as unavailable.
I would be happy to hear if somebody was able to get this working. We successfully proxy several other external repositories.
The problem was that we ran Nexus using an old Java 6 version. Java threw an exception which seems to be related to SSL communication. Running Nexus using Java 8 solved the problem for us.
I've added https://repo.eclipse.org/content/repositories/paho-releases/ as a proxy repository in Nexus and added it to the public group. Nexus blocked it as an untrusted remote, so I disabled auto-blocking. However, I can't download org.eclipse.paho:mqtt-client:0.4.0, which is available there. And when I open Browse Remote tab for this repository, the tree is empty. Is it necessary to add the SSL certificate despite disabling auto-blocking?
Yes. If you access the repository via https you need to register the certificate. If you are using Nexus OSS you have to do that in the JVM running Nexus. With Nexus Professional you can do that in the SSL user interface. Detailed documentation is in the Nexus book.