[ https://ovirt-jira.atlassian.net/browse/OVIRT-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22176#comment-22176 ] Juan Hernández commented on OVIRT-750: -------------------------------------- I believe that artifactory has a timeout that controls this timeout. When it tries to retrieve an artifact from an remote repository (Maven Central, for example) and it fails, it won't try again till the timeout expires. The default value is 43200 seconds, 12 hours, see "Missed Retrieval Cache Period" here: https://www.jfrog.com/confluence/display/RTF/Advanced+Settings I'd suggest to reduce this timeout, 12 hours is too high. It is also good practice, in my opinion, to wait till the artifacts are available in Maven Central before submitting the patches that use them to gerrit. This way you avoid this timeout completely. For example, when I release version 4.1.5 of the API model I wait till it is available here: http://central.maven.org/maven2/org/ovirt/engine/api/model/4.1.5/ Only when it is there I submit to gerrit the patches that use it.

Issues with mvn central syncrhronization ----------------------------------------

Key: OVIRT-750 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-750 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Piotr Kliczewski Assignee: infra

When I release new version of jsonrpc and update the engine to use it the build fails and it is required to manually perform refresh of artifactory cache.

-- This message was sent by Atlassian JIRA (v1000.482.3#100017)