hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dima Spivak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16050) Fully document site building procedure
Date Fri, 17 Jun 2016 00:11:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335040#comment-15335040

Dima Spivak commented on HBASE-16050:

So I think the email that gets sent out to dev@ (subject line: "Successful: HBase Generate
Website") has all the instructions on how to actually push it the site live after the Jenkins
job that sends that email builds the artifacts. Perhaps it would be a good idea to replace
the details in the ref guide of what the [hbase_generate_website Jenkins job|https://builds.apache.org/job/hbase_generate_website/]
does, to just say "Go run this job?" At the moment, there's that gap between people in-the-know
(i.e. [~misty], who built all this awesome automation to make life easy) and people who've
never pushed the site live before that we can try to reduce the friction for.

> Fully document site building procedure
> --------------------------------------
>                 Key: HBASE-16050
>                 URL: https://issues.apache.org/jira/browse/HBASE-16050
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Andrew Purtell
> On HBASE-15977 it's apparent some of us don't know how to publish the site now that we've
switched to gitpubsub and the documentation on the process is incomplete. 
> I followed the instructions starting here: http://hbase.apache.org/book.html#website_publish

> Nothing happened.
> What comes after step 3 "Add and commit your changes"? This needs to be documented end
to end and something every committer on the project (or, certainly, PMC) can accomplish. 

This message was sent by Atlassian JIRA

View raw message