On Tue, Aug 21, 2018 at 4:13 AM Robert Varga <[email protected]> wrote: > On 21/08/18 07:35, Ariel Adam wrote: > > Shaleen, any idea what this problem is? > > > > [ERROR] Failed to execute goal on project daexim-impl: Could not resolve > > dependencies for project > > org.opendaylight.daexim:daexim-impl:bundle:1.3.4: Failed to collect > > dependencies at com.jayway.jsonpath:json-path-assert:jar:2.2.0: Failed > > to read artifact descriptor for > > com.jayway.jsonpath:json-path-assert:jar:2.2.0: Could not transfer > > artifact com.jayway.jsonpath:json-path-assert:pom:2.2.0 from/to > > opendaylight-mirror > > (https://nexus.opendaylight.org/content/repositories/public/): Network > > is unreachable (connect failed) -> [Help 1] > > Yet another nexus issue, +infrastructure. > > Guys, do we have an idea why these are happening? >
Is this happening frequently? This was the only instance I've seen of it failing to transfer from Nexus in all autorelease-release jobs for the past week. We should track network issues in a spreadsheet or something so that we can keep record of how often it's happening. Something we could look into doing for the autorelease job is having it pre-download it's artifacts at the beginning of the job using something like "dependency:go-offline" to minimize the amount of artifacts it has to download during the build itself so that network blips are less likely to affect the job. Regards, Thanh
_______________________________________________ infrastructure mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/infrastructure
