Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
Description
website generation has been failing since Feb 20th
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
The status email says
Build status: Still Failing The HBase website has not been updated to incorporate HBase commit ${CURRENT_HBASE_COMMIT}.
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
Attachments
Attachments
Issue Links
- is broken by
-
HBASE-20032 Receving multiple warnings for missing reporting.plugins.plugin.version
- Resolved
- is duplicated by
-
HBASE-20076 Maven site generation fails
- Resolved
- links to