[
https://issues.apache.org/jira/browse/HBASE-16050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335057#comment-15335057
]
Andrew Purtell commented on HBASE-16050:
----------------------------------------
Is there a document that walks through how gitpubsub works? I am now sure that
I have no idea. Checking in isn't sufficient? This is a huge surprise.
svnpubsub "just works" after you check changes in.
We rely on a Jenkins job to actually publish the site? What happens if Jenkins
is unavailable, or the job configuration is lost, or someone with
hudson-jobadmin accidentally corrupts it?
I think we must have a way to generate and publish the site end to end from the
developer desktop. This can be handled by placing a script into dev-support/
that can do the equivalent of the Jenkins job.
Apologies that I was somehow totally absent earlier. Now getting involved due
to contact friction :-/
> 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)
