[
https://issues.apache.org/jira/browse/HBASE-16050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336738#comment-15336738
]
Andrew Purtell commented on HBASE-16050:
----------------------------------------
bq. when that's in place, the fall back plan in the case of a jenkins outage
will be committers manually pushing things, basically as they do now
Sounds good.
By the way I want to state for the record that I think a Jenkins job to
validate site build is a great thing to have, when Jenkins is available.
> 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
(v6.3.4#6332)