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

Hudson commented on HBASE-20070:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4677 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/4677/])
HBASE-20070 refactor website generation (busbey: rev 
2a65066b350c8354b09d3e57b8fdac644020faee)
* (edit) hbase-hadoop-compat/pom.xml
* (edit) hbase-client/pom.xml
* (edit) hbase-thrift/pom.xml
* (edit) hbase-metrics/pom.xml
* (edit) hbase-protocol/pom.xml
* (edit) hbase-it/pom.xml
* (edit) hbase-procedure/pom.xml
* (edit) dev-support/jenkins-scripts/generate-hbase-website.sh
* (edit) hbase-backup/pom.xml
* (edit) hbase-shell/pom.xml
* (edit) pom.xml
* (edit) hbase-assembly/pom.xml
* (edit) hbase-resource-bundle/pom.xml
* (edit) hbase-build-configuration/pom.xml
* (edit) hbase-mapreduce/pom.xml
* (edit) hbase-server/pom.xml
* (edit) hbase-spark-it/pom.xml
* (edit) hbase-endpoint/pom.xml
* (edit) hbase-replication/pom.xml
* (edit) hbase-common/pom.xml
* (edit) hbase-external-blockcache/pom.xml
* (edit) hbase-annotations/pom.xml
* (edit) hbase-metrics-api/pom.xml
* (edit) hbase-testing-util/pom.xml
* (edit) hbase-shaded/pom.xml
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
* (edit) hbase-hadoop2-compat/pom.xml
* (edit) hbase-rest/pom.xml
* (edit) hbase-http/pom.xml
* (edit) hbase-examples/pom.xml
* (edit) hbase-rsgroup/pom.xml
* (edit) hbase-zookeeper/pom.xml
* (edit) hbase-protocol-shaded/pom.xml


> website generation is failing
> -----------------------------
>
>                 Key: HBASE-20070
>                 URL: https://issues.apache.org/jira/browse/HBASE-20070
>             Project: HBase
>          Issue Type: Bug
>          Components: website
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>             Fix For: 3.0.0, 2.0.0-beta-2
>
>         Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1, 
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch, 
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch, 
> HBASE-20070.5.patch, HBASE-20070.6.patch, HBASE-20070.7.patch, 
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
>  is not yet mentioned in the hbase-site commit log. Assuming we don't have it 
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; 
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit 
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable 
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm 
> guessing the version of git changed on the build hosts and upended our 
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as 
> soon as that git command fails



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to