Project

General

Profile

Feature #6869

mirror the FWD dependencies in a proj.goldencode.com repository

Added by Constantin Asofiei almost 4 years ago. Updated 5 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Constantin Asofiei almost 4 years ago

gradle relies on 3rd party repositories like jboss, maven, oracle, jitpack.

Today, jitpack seems down (https://jitpack.io/com/github/jeremyh/jBCrypt/jbcrypt-0.4/jBCrypt-jbcrypt-0.4.pom is not working), and FWD will not be able to build on a clean machine (where there is no prior cached jars in the ~/.gradle folder).

We should build a mirror of all FWD dependencies on proj.goldencode.com/artifacts (or /repository), and let gradle fallback to this, if some dependency can not be resolved. A point is the GCD repository should not be the main repo, but a secondary one, in case the default/main one is down.

#2 Updated by Constantin Asofiei 5 days ago

This is a problem again - jitpack.io is down and I can't build on a virtual machine (I'll copy the .gradle folder manually from the host):

   > Could not resolve virtualscroller:virtualscroller:1.
     Required by:
         root project '10614_main'
      > Could not resolve virtualscroller:virtualscroller:1.
         > Could not get resource 'https://jitpack.io/virtualscroller/virtualscroller/1/virtualscroller-1.pom'.
            > Could not GET 'https://jitpack.io/virtualscroller/virtualscroller/1/virtualscroller-1.pom'.
               > Read timed out
> There are 2 more failures with identical causes.

We need to mirror (as a second-level repo, not the main repo) the gradle depencies.

Or at the last include the .gradle folder in the 'basedev' docker image used by fbash.sh or dbash.sh

Also available in: Atom PDF