[
https://issues.apache.org/jira/browse/SPARK-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265355#comment-14265355
]
Ryan Williams commented on SPARK-1517:
--------------------------------------
Hey [~pwendell], any updates here? The disconnect between the content of the
github README and the "/latest/" published docs leading up to the 1.2.0 release
continues to cast a shadow and new divergence is set to begin as we move
further from having just cut a release.
As was [recently pointed out on the dev
list|http://apache-spark-developers-list.1001551.n3.nabble.com/Starting-with-Spark-tp9908p9925.html],
[my|https://github.com/apache/spark/commit/4ceb048b38949dd0a909d2ee6777607341c9c93a#diff-04c6e90faac2675aa89e2176d2eec7d8]
and
[Reynold's|https://github.com/apache/spark/commit/342b57db66e379c475daf5399baf680ff42b87c2#diff-04c6e90faac2675aa89e2176d2eec7d8]
"fixes" to previously-broken links in the README became broken links when the
1.2.0 docs were cut, as [~srowen] [warned would
happen|https://github.com/apache/spark/commit/342b57db66e379c475daf5399baf680ff42b87c2#commitcomment-8250912]
(one is fixed [here|https://github.com/apache/spark/pull/3802/files], the
other remains broken on the README today).
I still believe that the correct fix is to have the README point at docs that
are published with each Jenkins build, per this JIRA and [our previous
discussion about
it|http://apache-spark-developers-list.1001551.n3.nabble.com/Spurious-test-failures-testing-best-practices-tt9560.html#a9568].
Even better would be to publish nightly docs *and* remove any pretense that the
github README is a canonical source of documentation, in favor of just linking
to the /latest/ published docs. Let me know if you want me to file that as a
sub-task here.
> 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]
