Sean Busbey commented on HBASE-20070:

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

How does this mechanism work? Why we have to set snippet in 
hbase-annotations/pom.xml and hbase-shaded-check-invariants/pom.xml ?

Some of the modules don't have {{hbase-build-configuration}} as a parent pom, 
so they don't inherit the skip flag for maven site. IIRC, {{hbase-annotations}} 
doesn't have it as a parent so that we can reference that module within the 
{{hbase-build-configuration}} configs. {{hbase-shaded-check-invariants}} maybe 
doesn't because it doesn't involve building any code?

> 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 
> {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

Reply via email to