[
https://issues.apache.org/jira/browse/SPARK-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660796#comment-14660796
]
Patrick Wendell commented on SPARK-1517:
----------------------------------------
Hey Ryan,
IIRC - the Apache snapshot repository won't let us publish binaries that do not
have SNAPSHOT in the version number. The reason is it expects to see
timestamped snapshots so its garbage collection mechanism can work. We could
look at adding sha1 hashes, before SNAPSHOT, but I think there is some chance
this would break their cleanup.
In terms of posting more binaries - I can look at whether Databricks or
Berkeley might be able to donate S3 resources for this, but it would have to be
clearly maintained by those organizations and not branded as official Apache
releases or anything like that.
> Publish nightly snapshots of documentation, maven artifacts, and binary builds
> ------------------------------------------------------------------------------
>
> Key: SPARK-1517
> URL: https://issues.apache.org/jira/browse/SPARK-1517
> Project: Spark
> Issue Type: Improvement
> Components: Build, Project Infra
> Reporter: Patrick Wendell
> Assignee: Patrick Wendell
> Priority: Critical
>
> Should be pretty easy to do with Jenkins. The only thing I can think of that
> would be tricky is to set up credentials so that jenkins can publish this
> stuff somewhere on apache infra.
> Ideally we don't want to have to put a private key on every jenkins box
> (since they are otherwise pretty stateless). One idea is to encrypt these
> credentials with a passphrase and post them somewhere publicly visible. Then
> the jenkins build can download the credentials provided we set a passphrase
> in an environment variable in jenkins. There may be simpler solutions as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
