You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Brian Fox (JIRA)" <ji...@apache.org> on 2015/04/03 00:54:53 UTC

[jira] [Closed] (INFRA-9363) Nexus SNAPSHOT deployment fails consistently

     [ https://issues.apache.org/jira/browse/INFRA-9363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fox closed INFRA-9363.
----------------------------
    Resolution: Fixed

> Nexus SNAPSHOT deployment fails consistently
> --------------------------------------------
>
>                 Key: INFRA-9363
>                 URL: https://issues.apache.org/jira/browse/INFRA-9363
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Nexus
>            Reporter: Robert Munteanu
>
> In the Apache Sling we have a Jenkins job which deploys SNAPSHOT artifacts to repository.apache.org. On Mar 30 2015 at around 09:30 AM deployment started failing with 
> [WARNING] Could not transfer metadata org.apache.sling:org.apache.sling.event:3.5.5-SNAPSHOT/maven-metadata.xml from/to apache.snapshots.https (https://repository.apache.org/content/repositories/snapshots): peer not authenticated
> This is not related to a single Jenkins slave, the failures are distributed:
> * https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/3229/ - H10
> * https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/3230/ - ubuntu-6
> * https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/3237/ - ubuntu-2
> This does not happen for projects which use Nexus just for retrieving dependencies, only for those deploying SNAPSHOT artifacts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)