[RTFACT-17463] Artifactory virtual repo should always fetch the latest packages or artifacts Created: 05/Sep/18  Updated: 17/Sep/18

Status: Open
Project: Artifactory Binary Repository
Component/s: None
Affects Version/s: 6.1.0, 6.2.0, 6.3.0
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Joon Lee (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None


Currently, the order of priority in our virtual repo for fetching the package requested by the client is

  1. Local
  2. remote cache
  3. remote

The use case, for example, assume the customer is working on an opensource project where their developers from around the globe are using the same package type with different versions that they published to local repo but when the latest final version eventually makes it to the remote repo, NPM download request through Artifactory still fetches the older version from the local repo because local takes precedent. 

I think Artifactory should be able to run the version check against all repos in the virtual for the latest package to allow the client to resolve the latest package version. 

Generated at Tue Aug 11 16:54:15 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.