I think this failure was a temporary Jenkins problem. Kicked off another build.
On Thu, Apr 7, 2016 at 8:07 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Build status: Failure > > If successful, the website and docs have been generated. If failed, skip > to the bottom of this email. > > Use the following commands to download the patch and apply it to a clean > branch based on origin/asf-site. If you prefer to keep the hbase-site repo > around permanently, you can skip the clone step. > > git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git > > cd hbase-site > wget -O- > https://builds.apache.org/job/hbase_generate_website/191/artifact/website.patch.zip > | funzip > ${GIT_SHA}.patch > git fetch > git checkout -b asf-site-${GIT_SHA} origin/asf-site > git am $GIT_SHA.patch > > At this point, you can preview the changes by opening index.html or any of > the other HTML pages in your local asf-site-${GIT_SHA} branch, and you can > review the differences by running: > > git diff origin/asf-site > > There are lots of spurious changes, such as timestamps and CSS styles in > tables. To see a list of files that have been added, deleted, renamed, > changed type, or are otherwise interesting, use the following command: > > git diff --name-status --diff-filter=ADCRTXUB origin/asf-site > > To see only files that had 100 or more lines changed: > > git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}' > > When you are satisfied, publish your changes to origin/asf-site using this > command: > > git push origin asf-site-${GIT_SHA}:asf-site > > Changes take a couple of minutes to be propagated. You can then remove > your asf-site-${GIT_SHA} branch: > > git checkout asf-site && git branch -d asf-site-${GIT_SHA} > > > > If failed, see > https://builds.apache.org/job/hbase_generate_website/191/console
