Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Date: Tue, 21 Apr 2015 16:21:58 +0000 (UTC)
From: "Brian Fox (JIRA)" <jira@apache.org>
To: builds@apache.org
Message-ID: <JIRA.12821805.1429258445000.63260.1429633318945@Atlassian.JIRA>
In-Reply-To: <JIRA.12821805.1429258445000@Atlassian.JIRA>
References: <JIRA.12821805.1429258445000@Atlassian.JIRA>
 <JIRA.12821805.1429258445305@arcas>
Subject: [jira] [Commented] (BUILDS-72) Deployment to Maven snapshot
 repository fails with "peer not authenticated"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/BUILDS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505207#comment-14505207 ] 

Brian Fox commented on BUILDS-72:
---------------------------------

We reverted back to the original ssl proxy system. It's still unclear why this is failing because I can deploy and stage no problem through the new box.

> Deployment to Maven snapshot repository fails with "peer not authenticated"
> ---------------------------------------------------------------------------
>
>                 Key: BUILDS-72
>                 URL: https://issues.apache.org/jira/browse/BUILDS-72
>             Project: Infra Build Platform
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Andreas Veithen
>
> The Apache Axiom build (https://builds.apache.org/job/ws-axiom-trunk/) recently started failing with a "peer not authenticated" error when trying to deploy artifacts to the snapshot repository. This appears to be some SSL related problem. Note that it only seems to occur on certain executors.


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