Good day all,

We are trying to understand exactly how we can ensure objects/ artifacts (once 
they are replicated to remote Artifactory instance) will be pulled from remote 
Artifactory instance that is local to the replicated location, and not from the 
original server where the object was originally deployed.
We want to ensure users (as well as our automated build scripts) in Europe will 
pull (new/ changed) objects that were replicated to European Artifactory 
servers, and will NOT be pulled from the Artifactory server back in the United 
States where the original local repo resides.

How is that typically done? How are the different repository types (local, 
remote, virtual) used in this setup?

i.e.

*         Developer 1 (US):                            -creates a SCM repo (in 
Bitbucket) with a .lfsconfig file containing the 'local-testrepo' url for 
Artifactory.
[lfs]
url = "http://artifactory:XXXX/artifactory/api/lfs/extern-local";

*         Developer 1 (US):                            -pushes new or changed 
code that lands in the US local-testrepo, and is then replicated to Europe 
Artifactory server repo.

*         Developer 2 (EU):                            -retrieves the new code 
from European Artifactory server

o   Automated script:           -retrieves the new code from European 
Artifactory server

*         Developer 2 (EU):                            -pushes his code changes 
to European Artifactory server (which are replicated back to US, OR are pushed 
(via git) directly back to US)


Thanks for any help you can provide, and please let me know if you need further 
info.

-K

------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply via email to