spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Commented] (SPARK-1517) Publish nightly snapshots of documentation, maven artifacts, and binary builds
Date Tue, 06 Jan 2015 00:11:34 GMT


Sean Owen commented on SPARK-1517:

Recap: old URL was "building-with-maven.html", new URL is "building-spark.html" to match a
rename and content change of the page itself a few months ago. There should be a redirect
from the former to latter. Until the 1.2.0 site was published, there was no building-spark.html
page live on the site. So had to link to building-with-maven.html, with the intent
that after 1.2.0 this would just redirect to building-spark.html.

I'm not sure why, but the redirect isn't working. It redirects to
. It seems like this is some default mechanism, and the redirector that the plugin is supposed
to generate isn't present or something. Could somehow be my mistake but I certainly recall
it worked on my local build of the site or else I never would have proposed it.

So yes one direct hotfix is to change links to the old page to links to the new page. Only
one of two links in was updated. It's easy to fix the other.

The that you see on is always going to be from master, but people are
going to encounter the page and sometimes expect it corresponds to a latest stable release.
(You can always view from the branch you want of course, if you know what you're
doing.) Yes, for this reason I agree that it's best to make it mostly pointers to other information,
and I think that was already the intent of changes that included the renaming I alluded to
above. IIRC there was a desire to not strip down further and leave some minimal,
hopefully fairly unchanging, info there.

Whether there should be nightly builds of the site is a different question. If you linked
to "nightly" instead of "latest" I suppose you'd have more of the same problem, no? people
finding the github site and perhaps thinking they are seeing latest stable docs? On the other
hand, it would at least be more internally consistent. On the other other hand, would you
have to change the links to the stable URLs for release and then back as part of the release
process? I had thought just linking to latest stable release docs was simple and fine.

> Publish nightly snapshots of documentation, maven artifacts, and binary builds
> ------------------------------------------------------------------------------
>                 Key: SPARK-1517
>                 URL:
>             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
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message