[ https://issues.apache.org/jira/browse/SPARK-7521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen resolved SPARK-7521. ------------------------------- Resolution: Fixed Resolving as fixed now that the new release scripts have been merged into Spark. > Allow all required release credentials to be specified with env vars > -------------------------------------------------------------------- > > Key: SPARK-7521 > URL: https://issues.apache.org/jira/browse/SPARK-7521 > Project: Spark > Issue Type: Sub-task > Components: Project Infra > Reporter: Patrick Wendell > Assignee: Patrick Wendell > > When creating releases the following credentials are needed: > 1. ASF private key, to post artifacts on people.apache. > 2. ASF username and password, to publish to maven and push tags to github. > 3. GPG private key and key password, to sign releases. > Right now the assumption is that these are made present in the build > environment through env vars, installed the GPG and private keys, etc. This > makes it difficult for us to automate the build, such as allowing the full > build+publish to occur on any Jenkins machine. > One way to fix this is to make sure all of these can be specified as env vars > which can then be securely threaded through to the jenkins builder. The > script itself would then e.g. create temporary GPG keys and RSA private key > for each build, using these env vars. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org