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-18348) SVN credentials for SVN deploy process triggered via CI?
Date Wed, 05 Jun 2019 01:40:00 GMT

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

Chris Lambertus commented on INFRA-18348:
-----------------------------------------

We are (still) working on documentation and a process for projects to use to deploy websites,
but other projects have done so. We offer a jenkins build node labelled git-websites which
allows projects to push to an asf-site branch from a jenkins job. I believe this also exists
in svn, but I'd have to get back to you on the specifics. We do not support pushing sites
from travis at this time. I will flag this for review at the next Infra discussion.


> SVN credentials for SVN deploy process triggered via CI?
> --------------------------------------------------------
>
>                 Key: INFRA-18348
>                 URL: https://issues.apache.org/jira/browse/INFRA-18348
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: CI
>            Reporter: Jan Piotrowski (janpio)
>            Priority: Minor
>
> Over at https://github.com/apache/cordova-docs, which is the source for https://cordova.apache.org/,
we have a build process that deploys the built website to SVN when commits are merged to master
(source at https://github.com/apache/cordova-docs/blob/master/buildAndDeploy.sh).
> Recently this broke because the SVN credentials stored via https://travis-ci.org/apache/cordova-docs/settings
and used in the deploy script were locked. 
> ```
> svn: E215004: Authentication failed and interactive prompting is disabled; see the --force-interactive
option
> svn: E215004: Commit failed (details follow):
> svn: E215004: No more credentials or we tried too many times.
> Authentication failed
> ```
> As the committer whose credentials were used is not reachable, I just replaced them with
mine. But to be honest, 1) I am not sure if those will get blocked now as well (if our deploy
process is messed up somehow) and 2) I am not super comfortable that now _all_ automated deploys
will be attributed to me on SVN. This just feels wrong.
> Is there a better was to solve this problem? Is there a way to have user account independent
SVN credentials for this deploy to SVN?
> Thanks.
> (I didn't create this deploy process and script, I am just trying to get it fixed somehow
as I just wasted an hour first trying to find out why our documentation didn't get properly
updated)



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

Mime
View raw message