[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378019#comment-16378019
]
Sean Busbey commented on HBASE-20070:
-------------------------------------
I figured it out!
HBASE-20032 changed it so that we're using {{maven-javadoc-plugin}} version
3.0.0 for reports, which is when the actual site goal started failing on
jenkins. prior to that, wether mvnsite worked or not would depend on the maven
version you had, since we weren't specifying a version for the
{{maven-javadoc-plugin}}. version 3.0.0 of the javadoc plugin removed the
configuration value we use to turn off the javadoc linter in MJAVADOC-474. They
added the ability to directly configure the doclint setting via MJAVADOC-387
and made a new way to give custom javadoc parameters in MJAVADOC-475.
Unfortunately, nothing in the maven output makes this obvious.
Everything not in the site generation is still working because in all those
cases we're still using {{maven-javadoc-plugin}} version 2.10.3.
ugh. what a mess.
I'll get a new patch that a) updates our use of maven-javadoc-plugin to match
in non-report contexts, b) consistently disables the linter.
> 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
> 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-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)
