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 Tue, 14 Mar 2017 00:15:41 GMT

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

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

One more thing to add, being that Tika just kicked up on those nodes, we just added windows-2012-3
as a new build server. There is an ever so slight chance that the build might hiccup on that
box due to missing configs. Just make sure the check the build logs for the node before diving
too deep into troubleshooting a build.

> 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