We have our apache maven repository hosted on a server and we are using nexus to have this as a proxy repository. I want to upload some new artifacts to this public apache maven repository so that It gets reflected on nexus, and that my projects can use that. But I am not being able to find a method to do so.
Related
We want to mirror PowerShell module repository in to our Artifactory instance as a Virtual repo, to have the ability to obtain needed modules from our Azure VM
Has any one done that before? Is there any documentation on how to mirror PowerShell modules into Artifactory?
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
Could someone please explain what's are these 3 types of repos local, remote and virtual in JFrog Artifactory. , I'm not getting a clear picture of it from JFrog Artifactory documentation.
https://www.jfrog.com/confluence/display/RTF/Configuring+Repositories
Local repositories are physical, locally-managed repositories into which you can deploy artifacts.
A remote repository serves as a caching proxy for a repository managed at a remote URL (which may itself be another Artifactory remote repository).
Artifacts are stored and updated in remote repositories according to various configuration parameters that control the caching and proxying behavior. You can remove artifacts from a remote repository cache but you cannot actually deploy a new artifact into a remote repository.
A virtual repository (or "repository group") aggregates several repositories with the same package type under a common URL.
Bamboo supports shared credentials.
I would like to use these shared credentials to commit tags to git using the artifactory maven addon.
According to this ticket: https://www.jfrog.com/jira/browse/BAP-189 it should work.
I do however not know where to configure it.
We are using bamboo 5.14.3.1
Artifactory plugin 2.1.0
Was this feature removed?
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.