[
https://issues.apache.org/jira/browse/BEAM-6544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755577#comment-16755577
]
Robert Bradshaw commented on BEAM-6544:
---------------------------------------
Strongly agree, I thought we had taken care of this.
What we need is a place to push things. Generally pushing blobs to publicly
accessible places require credentials. One option is asking for
(non-individual) apache credentials that have push permissions to svn (or
somewhere else apache hosted). These are encrypted so travis can see them, but
others can't. Short of that we could try to push them elsewhere (e.g. gcs,
similar to how we allow our robot accounts to write there for tests) and then
manually copy the to the svn directory.
> Python wheel release process must not require inputting credentials to third
> party sites
> ----------------------------------------------------------------------------------------
>
> Key: BEAM-6544
> URL: https://issues.apache.org/jira/browse/BEAM-6544
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Kenneth Knowles
> Assignee: Luke Cwik
> Priority: Blocker
>
> According to the instructions at
> https://beam.apache.org/contribute/release-guide/#build-and-stage-python-wheels
> and https://github.com/apache/beam-wheels, the release manager must input
> their ASF credentials to Travis-CI. This should not be required.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
