You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2018/02/24 16:54:01 UTC
[jira] [Created] (HBASE-20070) website generation is failing
Sean Busbey created HBASE-20070:
-----------------------------------
Summary: 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
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)