hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-20070) website generation is failing
Date Thu, 01 Mar 2018 18:57:00 GMT

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

Sean Busbey commented on HBASE-20070:


  - make the git diff skip the use of a pager by teeing to a log file

  - avoid duplicative site executions (each of which causes a 4x duplicate of building the
project), mostly by relying on skipping in hbase-build-configuration

  - correct the name of log files to reflect that we're installing locally and then running
site (rather than 'build' and 'install')

  - skip the enforcer plugin all the time, we don't need to repeat that in the website build

  - skip the compiler plugin in our site invocation, since we just installed everything we
don't need the forked javadoc compile to build stuff.


looks like this set of changes also gets through the website generation in something like
half or maybe even a third of the time?

> 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-20070.4.patch,
HBASE-20070.5.patch, HBASE-20070.6.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

View raw message