[
https://issues.apache.org/jira/browse/SPARK-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265419#comment-14265419
]
Ryan Williams commented on SPARK-1517:
--------------------------------------
Agreed that the redirect you speak of should exist / be fixed; a separate JIRA
should be filed for that.
bq. Whether there should be nightly builds of the site is a different question.
My understanding is that there has been consensus at a few points that this is
a good idea. The main concern you've voiced is the risk that people will land
on the github README when looking for stable/release docs, and:
# find "nightly" info directly in the README content (and not understand it to
be incorrect (too up-to-date) for their purposes), or
# inadvertently follow a link to published "nightly" docs.
re: 1, in my last post I suggested doing away with the pretense that the github
README will directly contain Spark documentation, and replacing its current
content with links to the relevant published docs, potentially *both* nightly
and stable.
re: 2, as long as the README's links to "nightly" and "stable" docs sites are
clearly marked, this should not be a problem. Users already must have a minimal
level of understanding of what version of Spark docs they want to look at.
> 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
> Priority: Blocker
>
> 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]
