infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Thistlethwaite (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-13647) Deploy to https://repository.apache.org fails on Windows build slaves
Date Mon, 13 Mar 2017 16:52:41 GMT

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

Chris Thistlethwaite commented on INFRA-13647:
----------------------------------------------

Well that didn't fix it, but I'll leave this on -1 just so we can troubleshoot the build and
not the machine. Seems there are other builds (FlexJS Typedefs) that are working https://builds.apache.org/job/FlexJS%20Typedefs%20(maven)/

Looking at the two projects, the "post build" config for your project is different. Whereas
Flex has that info in the pom and not in Jenkins. 

> Deploy to https://repository.apache.org fails on Windows build slaves
> ---------------------------------------------------------------------
>
>                 Key: INFRA-13647
>                 URL: https://issues.apache.org/jira/browse/INFRA-13647
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Dave Meikle
>            Assignee: Chris Thistlethwaite
>            Priority: Minor
>
> We have a Windows build for Tika 2.x (https://builds.apache.org/view/Tika/job/tika-2.x-windows/)
using the Windows label.
> For these builds we are seeing a 401 error for deployment transfers to https://repository.apache.org.
> We are wondering if the ID for this server is out of date in the Maven settings on those
nodes, as all our Ubuntu based builds are working correctly.
> Any help would be appreciated.
> Thanks,
> Dave



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message