[Artifactory-developers] [JFrog JIRA] Resolved: (RTFACT-401) Prevent failing builds by allowing pass-through of invalid metadata

[Yoav L. (JIRA) <ji...@jf...>]

     [ http://issues.jfrog.org/jira/browse/RTFACT-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yoav Landman resolved RTFACT-401.
---------------------------------

    Resolution: Fixed

Pom consistency checks are exposed on the UI on a per repo level.

> Prevent failing builds by allowing pass-through of invalid metadata
> -------------------------------------------------------------------
>
>                 Key: RTFACT-401
>                 URL: http://issues.jfrog.org/jira/browse/RTFACT-401
>             Project: Artifactory
>          Issue Type: Improvement
>          Components: Downloader
>    Affects Versions: 1.2.5u1
>         Environment: Any
>            Reporter: Richard Calmbach
>            Assignee: Yoav Landman
>             Fix For: 2.1.0
>
>
> The Internet Maven repositories will always contain some amount of invalid metadata due to human error. Artifactory by default does not cache invalid metadata to protect the integrity of the cache. This is A Good Thing. However, currently Artifactory does not even forward the invalid metadata to clients. This leads to problems worse than just invalid metadata: It causes Maven invocations that succeed *without* Artifactory in the artifact resolution chain to fail *with* Artifactory in the resolution chain. See RTFACT-387 for an example.
> My suggestion is that if Artifactory encounters invalid metadata in a remote repository (e.g., an invalid .pom), Artifactory should just pass the file through without caching it. That would result in a request to the remote repository every time that file is needed but it beats breaking a build that succeeds with unproxied Maven.
> Somewhere in the Artifactory GUI there could be a report section that lists all the invalid artifacts that have been encountered so that the proxy admin can upload corrected metadata to the local ext-* repositories in Artifactory if they so choose.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.jfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira