infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <>
Subject [jira] [Updated] (INFRA-17138) Apache Flink snapshot deployments fail
Date Fri, 12 Oct 2018 12:38:00 GMT


Gavin updated INFRA-17138:
    Status: Waiting for user  (was: Waiting for Infra)

your job is configured to use your own self provided credentials file [1] which is public,
so Im really glad we change the passwd, meaning your file is out of date. We are not going
to provide you the updated creds, but rather ask you change your build to use the standard
default maven settings.xml that is on every node we have.

Let me know how you get on

> Apache Flink snapshot deployments fail
> --------------------------------------
>                 Key: INFRA-17138
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Till Rohrmann
>            Assignee: Gavin
>            Priority: Major
> Since end of September the Flink snapshot deployment fail with 
> {{code}}
> [WARNING] Encountered issue during deployment: Failed to deploy artifacts: Could not
transfer artifact org.apache.flink:force-shading:jar:1.7-20181012.033357-70 from/to apache.snapshots.https
( Failed to transfer file:
Return code is: 401, ReasonPhrase: Unauthorized.
> {{code}}
> See here for more information:
> I was wondering whether there is a problem with authentication between Jenkins and the
Apache repository

This message was sent by Atlassian JIRA

View raw message