Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.basic.visual.misc > #3502

Artifactory Download From Remote Repository

Show all headers | View raw

If I am right up to this point, then practically it means you only need a remote repository for npm if you do not develop npm modules but only use them to build your application. In contrast, if you need to both pull and push Docker container images, you need to have one local repository for pushing&pulling custom images and one remote repository for pulling official images.


I am confused because our Artifactory admin created a local npm repository for our project. When I discussed the topic with him he told me that I need to first get packages from the internet to my PC and push them to Artifactory server. This does not make any sense to me because I have seen some remote repositories on the same server and what we need is only to pull packages from npm. Is there a point that I miss?



artifactory download from remote repository

Download File https://sorxeconni1979.blogspot.com/?oy=2wZlNY 






Are artifacts at remote repository cache saved until intentionally deleted? Is there a default retention policy (i.e. delete packages older than 6 months)? I ask this because it is important to keep packages until a meteor hits the servers (for archiving policy of the company).


We will need to get official Docker images and customize them for CI. It would be a bit hard to maintain one local repo for pulling&pushing custom images and one remote repo for pulling official images. Let's say I need to pull official Ubuntu latest, modify it, push and finally pull the custom image back. In this case it should be pulled using remote repository, pushed to local repo and pulled again from local repo. Is it possible to use virtual repositories to do this seamlessly as one repo?


Generally, you would want to use a remote repository for this. You would then point your client to this remote repository and JFrog Artifactory would grab them from the remote site and cache them locally, as needed.


It is also security-aware so if the user only has access to the local stuff and not the remote stuff, they will only be able to access the local stuff even though they are using the virtual repository that contains both of them.


I had jcenter repository in my artifactory under remote repositories. Since some of the artifacts were missing such as qpid, I decided to delete jcenter and add it back. When I deleted the jcenter repository and added it back it didn't download any artifacts.The repository tree structure looks like this


A remote repository in Artifactory serves as a caching proxy. This means that it downloads artifacts from the remote URL and cache them in Artifactory,

When you deleted the JCenter repository from Artifactory you deleted all cached artifacts.

After recreating the repository, your cache is empty. This is why, when browsing jcenter-cache, you see no artifacts. You can use the remote browsing capability in order to see which artifacts are available in the remote URL, but not currently caches

To re-populate the cache, you will need to download artifacts from the remote repository. Usually the best way to do it, is running your builds which are using this repository.If the problem is that artifacts are not resolved at all from the remote repository, try the following:


Deleting a repository is not a good practice when you are missing some dependencies. A better approach would be checking if they are available in the remote URL and downloading them into the cache. Artifactory has the option to perform a remote search in Bintray which can help you when looking for artifacts in JCenter.






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 _URL/ubuntu-remote/ and make sure the "store artifacts locally"is checked so that this remote repository can able to index the artifacts.


My employer has been misusing Bintray as our binary repository for some time. We are finally moving to Artifactory instead and closing down Bintray. But this seems to be an almost impossible task. There is no way of exporting Bintray repos to a zip. Downloading the repos means manually downloading each file from the UI or through their API. I have tried two approaches for automation:


1) wget for crawling our bintray like this:wget -e robots=off -o /wget.log -w 1 -m -np --user --password " "which yielded all of the files in the repos. But this only solves half the problem. I couldn't find out how to import the files to a repository in artifactory (all the repos are over 100mbs each and therefore can't be uploaded, for some reason).


2) I set the Bintray repos up as remote repositories and enabled Active Replication. That seems to have worked for now. But I don't know if they will be removed when the Bintray account is moved or even if they are stored in Artifactory. Therefore I would like to convert the remote repo to a local repo, to make sure that it is permanently stored in artifactory is there a way of doing this? If so, how?


Think of the case of a large number of developers in the company pulling Artefacts from Maven central. It creates a lot of network traffic across the internet, or possibly you have policies restricting this. To solve this we create a remote repository in Artifactory that acts like a proxy and local cache for Maven central. Now Maven can pull Artefacts from your remote repo in Artifactory and Artifactory will pull them from Maven Central. This also gives Artifactory the ability to scan artefacts and potentially take action based on vulnerabilities.


Think about someone else in the company wanting to use your Artefact in their project, but they also need stuff from Maven Central. They would need to pull from 2 repos. With a virtual repo you can effectively combine 2 or more repos into a single virtual repo. For the developer they just see the single repo but underneath it could be a local and remote repo. This would also be useful if you want to combine multiple remote repos, eg I've seen companies like Splunk and MapR have their own repos. Previously I would need to add these various repos into my POM file. Now I can just create a new remote repo in Artifactory and add that repo to my virtual repo.


In this case it's the Atlassian repository that has problems. I can't understand why when there's a "read timeout" problem or any I/O problem with a repository, the failed connection does not get cached by Artifactory, even if I set the "Failed Retrieval Cache Period" to 3600 seconds (that is, one hour) into all the remote repository. I would expect that, if a repository is not responding, Artifactory does not try to contact it again for an hour... Instead, it tries again and again, so that any request coming from Gradle takes a lot of time to be satisfied. I even lowered the "Socket Timeout" setting to 5 seconds on each repository, however this helps very little. 

Sometimes I'm forced to temporarily set the "Offline" mode on the "broken" repository in order to have Artifactory respond in a reasonable amount of time... But this is a workaround, since I then must remember that I have to re-enable it some time later...


Frederic Simon says that the Artifactory is keeping the "Failed Retrieval Cache Period" per path.

I think that if a remote repository is not responding, the cache period should be kept valid for the whole repository.


In summary, you have to create a remote repository pointing to the golang proxy, a virtual repository pointing to your remote repository, and conigure your client correctly. More detailed instructions follow.


It turns out, quite a long way down the instructions page, that Artifactory only supports resolution of Go packages from virtual Go repositories. To resolve Go from other local or remote Go repositories, you need to aggregate them in a virtual Go repository.


Remote repositories store artifacts from external sources such as Docker Hubor PyPI. A remote repository acts as a proxy for the external source so that youhave more control over your external dependencies. The first time that yourequest a version of a package, Artifact Registrydownloads and caches the package in the remote repository. The next time yourequest the same package version, Artifact Registry serves the cached copy.


For example, the following command creates a remote repository namedmy-repo in the region us-east1 in the Google Cloud projectmy-project and can authenticate to the upstream repository using theusername my-username and secret versionprojects/my-project/secrets/my-secret/versions/1.


For example, the following command creates a remote repository namedmy-repo to cache the Debian buster repository in the region us-east1 inthe Google Cloud project my-project. The full URL of the upstreamrepository is


For example, the following command creates a remote repository for Yum packagesnamed my-repo in the region us-east1 in the Google Cloud projectmy-project for the upstream repository centos/8-stream/BaseOs/x86_64/os.


Under Default Deployment Repository, select workshop-docker-prod-local as the default deployment repository. This means that image deployments from virtual repository workshop-docker will actually deploy from the local repository workshop-docker-prod-local.


Hi FWord3

We have some amazing news for you!

We recently released our brand new HuggingFace dedicated local and remote repositories which are just the solution you are looking for.

We invite you to take a look at our documentation and to try it out as we have shared this as an open Beta for all our SaaS customers (available from Artifactory Version 7.69.4)


Same concept of the install:install-file goal of the maven-install-plugin where the 3rd party JAR is installed in the local repository. But this time instead to local repository the JAR will be install both in the local and remote repository.


If your Artifactory repository requires authentication, ensure that the user account to be used has both Read and Deploy/Cache permissions for both the package-manager-sync-remote and package-manager-sync-cached remote repositories.

 35fe9a5643

Back to comp.lang.basic.visual.misc | Previous | Next | Find similar

Thread

Artifactory Download From Remote Repository Vilfredo Falls <vilfredofalls@gmail.com> - 2023-12-30 17:02 -0800

csiph-web