infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17087) UIMA Jenkins builds unable to deploy to repo
Date Sat, 06 Oct 2018 18:30:00 GMT

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

Chris Lambertus commented on INFRA-17087:
-----------------------------------------

Very strange.. we had a situation where some of the slaves weren't getting an updated credential,
but that problem has been resolved (and nobody else has mentioned snapshot upload failures
since.) I wonder if UIMA is doing something differently to publish snapshots? Where is it
getting the user/pass for apache.snapshots.https from? It should be coming from ~jenkins/.m2/settings.xml.


> UIMA Jenkins builds unable to deploy to repo
> --------------------------------------------
>
>                 Key: INFRA-17087
>                 URL: https://issues.apache.org/jira/browse/INFRA-17087
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Richard Eckart de Castilho
>            Assignee: Chris Lambertus
>            Priority: Major
>
> Recent builds of the UIMA project on the Apache Jenkins (since minimum Oct 1 2018) are
unable to deploy their artifacts to the Maven repo:
> {noformat}
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://repository.apache.org/content/repositories/snapshots/org/apache/uima/parent-pom/13-SNAPSHOT/parent-pom-13-20181003.080847-2.pom.
Return code is: 401, ReasonPhrase: Unauthorized.
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message