X-Received: by 2002:ac8:5903:0:b0:427:fa8c:e6ac with SMTP id 3-20020ac85903000000b00427fa8ce6acmr590154qty.1.1703984528149; Sat, 30 Dec 2023 17:02:08 -0800 (PST)
X-Received: by 2002:a05:690c:882:b0:5e6:27ee:67fb with SMTP id cd2-20020a05690c088200b005e627ee67fbmr6426135ywb.4.1703984527828; Sat, 30 Dec 2023 17:02:07 -0800 (PST)
Path: csiph.com!news.mixmin.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.basic.visual.misc
Date: Sat, 30 Dec 2023 17:02:07 -0800 (PST)
Injection-Info: google-groups.googlegroups.com; posting-host=2a09:f040:ad58:c363:e146:25b7:8211:6726; posting-account=Gf0POwoAAAD7D7oLd541HIyXZG3i8Ef8
NNTP-Posting-Host: 2a09:f040:ad58:c363:e146:25b7:8211:6726
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <159393f1-e1a4-483d-8ca0-3f004377cedbn@googlegroups.com>
Subject: Artifactory Download From Remote Repository
From: Vilfredo Falls <vilfredofalls@gmail.com>
Injection-Date: Sun, 31 Dec 2023 01:02:08 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: csiph.com comp.lang.basic.visual.misc:3502

If I am right up to this point, then practically it means you only need a r=
emote repository for npm if you do not develop npm modules but only use the=
m 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 image=
s.


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 Artifact=
ory server. This does not make any sense to me because I have seen some rem=
ote repositories on the same server and what we need is only to pull packag=
es from npm. Is there a point that I miss?



artifactory download from remote repository

Download File https://sorxeconni1979.blogspot.com/?oy=3D2wZlNY=20






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


We will need to get official Docker images and customize them for CI. It wo=
uld be a bit hard to maintain one local repo for pulling&pushing custom ima=
ges and one remote repo for pulling official images. Let's say I need to pu=
ll official Ubuntu latest, modify it, push and finally pull the custom imag=
e 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 th=
en 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 th=
em.


I had jcenter repository in my artifactory under remote repositories. Since=
 some of the artifacts were missing such as qpid, I decided to delete jcent=
er 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 th=
at it downloads artifacts from the remote URL and cache them in Artifactory=
,

When you deleted the JCenter repository from Artifactory you deleted all ca=
ched artifacts.

After recreating the repository, your cache is empty. This is why, when bro=
wsing 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 remo=
te 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 depe=
ndencies. 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 a=
rtifacts in JCenter.






I assume you are trying to set up a smart remote repository with Artifactor=
y. Refer to this wiki and set up the smart remote repository, basically, yo=
u 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 tim=
e. We are finally moving to Artifactory instead and closing down Bintray. B=
ut 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 e=
ach 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=3Doff -o /wget.lo=
g -w 1 -m -np --user --password " "which yielded all of the files in the re=
pos. But this only solves half the problem. I couldn't find out how to impo=
rt 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 Rep=
lication. 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 r=
epo, to make sure that it is permanently stored in artifactory is there a w=
ay of doing this? If so, how?


Think of the case of a large number of developers in the company pulling Ar=
tefacts 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 als=
o gives Artifactory the ability to scan artefacts and potentially take acti=
on based on vulnerabilities.


Think about someone else in the company wanting to use your Artefact in the=
ir 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 mo=
re repos into a single virtual repo. For the developer they just see the si=
ngle repo but underneath it could be a local and remote repo. This would al=
so be useful if you want to combine multiple remote repos, eg I've seen com=
panies like Splunk and MapR have their own repos. Previously I would need t=
o add these various repos into my POM file. Now I can just create a new rem=
ote 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 under=
stand why when there's a "read timeout" problem or any I/O problem with a r=
epository, the failed connection does not get cached by Artifactory, even i=
f I set the "Failed Retrieval Cache Period" to 3600 seconds (that is, one h=
our) into all the remote repository. I would expect that, if a repository i=
s 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 Gradl=
e 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.=20

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 t=
ime... 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 C=
ache Period" per path.

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


In summary, you have to create a remote repository pointing to the golang p=
roxy, 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 r=
esolve 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 Hu=
bor PyPI. A remote repository acts as a proxy for the external source so th=
at youhave more control over your external dependencies. The first time tha=
t yourequest a version of a package, Artifact Registrydownloads and caches =
the package in the remote repository. The next time yourequest the same pac=
kage 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 authe=
nticate 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 pack=
agesnamed my-repo in the region us-east1 in the Google Cloud projectmy-proj=
ect for the upstream repository centos/8-stream/BaseOs/x86_64/os.


Under Default Deployment Repository, select workshop-docker-prod-local as t=
he default deployment repository. This means that image deployments from vi=
rtual repository workshop-docker will actually deploy from the local reposi=
tory workshop-docker-prod-local.


Hi FWord3

We have some amazing news for you!

We recently released our brand new HuggingFace dedicated local and remote r=
epositories 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 h=
ave 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 w=
here 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 r=
emote repository.


If your Artifactory repository requires authentication, ensure that the use=
r account to be used has both Read and Deploy/Cache permissions for both th=
e package-manager-sync-remote and package-manager-sync-cached remote reposi=
tories.

 35fe9a5643