subject:"\[jira\] \[Commented\] \(HBASE\-20070\) website generation is failing"

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-05 Thread Mike Drob (JIRA)


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

Mike Drob commented on HBASE-20070:
---

Missed my opportunity to review here, filed HBASE-20134

> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.patch, 
> HBASE-20070.addendum.8.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-04 Thread Hudson (JIRA)


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

Hudson commented on HBASE-20070:


Results for branch master, done in 4 hr 28 min and counting
[build #249 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/249/]:

details (if available):

(x) *{color:red}-1 overall{color}*
Committer, please check your recent inclusion of a patch for this issue.









(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.patch, 
> HBASE-20070.addendum.8.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-04 Thread Hudson (JIRA)


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

Hudson commented on HBASE-20070:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4687 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/4687/])
HBASE-20070 addendum for missing echo. Website generation is failing. (appy: 
rev 485af49e53cb38e2af4635f2c3bc0b33e15ba0a1)
* (edit) dev-support/jenkins-scripts/generate-hbase-website.sh


> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.patch, 
> HBASE-20070.addendum.8.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-03 Thread Appy (JIRA)


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

Appy commented on HBASE-20070:
--

+1 on addendum

> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.patch, 
> HBASE-20070.addendum.8.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-03 Thread Hudson (JIRA)


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

Hudson commented on HBASE-20070:


Results for branch master, done in 4 hr 0 min and counting
[build #248 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/248/]:

details (if available):

(x) *{color:red}-1 overall{color}*
Committer, please check your recent inclusion of a patch for this issue.









(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.patch, 
> HBASE-20070.addendum.8.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on HBASE-20070:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
17s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
3s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 0s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
10s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}  0m 36s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20070 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12912862/HBASE-20070.addendum.8.patch
 |
| Optional Tests |  asflicense  shellcheck  shelldocs  |
| uname | Linux 46f74dec4a09 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9 
14:43:09 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 1d25b60831 |
| maven | version: Apache Maven 3.5.2 
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| shellcheck | v0.4.4 |
| Max. process+thread count | 42 (vs. ulimit of 1) |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11789/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.patch, 
> HBASE-20070.addendum.8.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on HBASE-20070:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
15s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
4s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
19s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  6m 
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  5m 
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
56s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  8m 
28s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  4m 
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  4m 
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 2s{color} | {color:green} The patch generated 0 new + 0 unchanged - 1 fixed = 
0 total (was 1) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green}  0m 
39s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
18s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
24m  1s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 12m 
30s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}207m 
44s{color} | {color:green} root in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 11m 
 5s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}294m 23s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20070 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12912787/HBASE-20070.7.patch |
| Optional Tests |  asflicense  shellcheck  shelldocs  javac  javadoc  unit  
shadedjars  hadoopcheck  xml  compile  |
| uname | Linux 2dfbd0ea2c44 3.13.0-133-generic #182-Ubuntu SMP Tue Sep 19 
15:49:21 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 99d3edfc82 |
| maven | version: Apache Maven 3.5.2 
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_151 |
| shellcheck | v0.4.4 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11776/testReport/ |
| Max. process+thread count | 4414 (vs. ulimit of 1) |
| modules | C: hbase-annotations hbase-build-configuration 
hbase-protocol-shaded

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Hudson (JIRA)


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

Hudson commented on HBASE-20070:


FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4677 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/4677/])
HBASE-20070 refactor website generation (busbey: rev 
2a65066b350c8354b09d3e57b8fdac644020faee)
* (edit) hbase-hadoop-compat/pom.xml
* (edit) hbase-client/pom.xml
* (edit) hbase-thrift/pom.xml
* (edit) hbase-metrics/pom.xml
* (edit) hbase-protocol/pom.xml
* (edit) hbase-it/pom.xml
* (edit) hbase-procedure/pom.xml
* (edit) dev-support/jenkins-scripts/generate-hbase-website.sh
* (edit) hbase-backup/pom.xml
* (edit) hbase-shell/pom.xml
* (edit) pom.xml
* (edit) hbase-assembly/pom.xml
* (edit) hbase-resource-bundle/pom.xml
* (edit) hbase-build-configuration/pom.xml
* (edit) hbase-mapreduce/pom.xml
* (edit) hbase-server/pom.xml
* (edit) hbase-spark-it/pom.xml
* (edit) hbase-endpoint/pom.xml
* (edit) hbase-replication/pom.xml
* (edit) hbase-common/pom.xml
* (edit) hbase-external-blockcache/pom.xml
* (edit) hbase-annotations/pom.xml
* (edit) hbase-metrics-api/pom.xml
* (edit) hbase-testing-util/pom.xml
* (edit) hbase-shaded/pom.xml
* (edit) hbase-shaded/hbase-shaded-check-invariants/pom.xml
* (edit) hbase-hadoop2-compat/pom.xml
* (edit) hbase-rest/pom.xml
* (edit) hbase-http/pom.xml
* (edit) hbase-examples/pom.xml
* (edit) hbase-rsgroup/pom.xml
* (edit) hbase-zookeeper/pom.xml
* (edit) hbase-protocol-shaded/pom.xml


> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread stack (JIRA)


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

stack commented on HBASE-20070:
---

I'm on it [~busbey] I've started a new build that includes your push. Thanks. 
Will report back.

I was running make_rc.sh. Thats how I found the problem. 

> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

{quote}
git version 2.7.4
fatal: 'refs/remotes/origin/HEAD' - not a valid ref
{quote}

Ugh. such an old version. I'll mess around with teh job later and get this to 
work.

> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

looking at the diff from HBASE-20032, I believe this patch will fix the issue 
you're having [~stack]. I suspect you're getting the same error I was getting 
in my tests.

> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

[~stack], I put the github PR up because it's [~misty]'s preference and she's 
been doing most of the review here.

Can you give me the command that fails for you on branch-2? I can test it out 
locally and see if there's an easy fix. what maven version are you using?

> 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
> Fix For: 3.0.0, 2.0.0-beta-2
>
> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread stack (JIRA)


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

stack commented on HBASE-20070:
---

What you see as benefits dev'ing against github making PRs [~busbey]? Thanks. 
You like going this route?

> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread stack (JIRA)


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

stack commented on HBASE-20070:
---

I'm +1.

This will fix my current problem cutting an RC? I can't make the RC w/o doing 
below revert and my sense is that this will fix it (Takes a while to verify).

commit b34f8f959ff5dc3d301128768dc5bf3e87205390
Author: Michael Stack 
Date:   Thu Mar 1 23:49:09 2018 -0800

Revert "HBASE-20032 Receving multiple warnings for missing 
reporting.plugins.plugin.version"

This reverts commit c5ca3c2fe6bdf25ef54f68e48d2d3629c06f37f7.

> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

(the github PR is also up to date with v7 here)

> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

-7 LGTM with code review (on Github) but I haven’t been able to test this 
locally. It would be nice if someone did a test run before foisting this on 
Jenkins. Remember the Jenkins job needs to be updated to run the script with 
the new syntax too.

> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

-7 feedback from github pr
  - add debug notes when we're using a default cli option
  - remove duplicative code comment
  - remove outdated jdk option that isn't needed in jdk8+
  - make it so {{--publish}} actually will push to the remote repo

> 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-20070.7.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

bq. Nice usage function.

thanks!

bq. none in general properties gets picked up by javadoc? 
Thats good.

yep. There was some talk in the {{maven-javadoc-plugin}} community about making 
the name better scoped, i.e. {{maven.javadoc.doclint}}, but AFAICT that change 
never happened. I really like that this property gets picked up both in the 
normal lifecycle ({{javadoc:javadoc}}) and in the site reporting section.

{quote}
This was just noise?

168 #echo "Dumping current environment:"
169 #env
{quote}
Since it was commented out I figured best to just remove it. I can add it back 
if you prefer. We should really have the job use the "gather machine stats" 
script if we want that kind of info though.

{quote}
...and this unnecessary work?

160 git fetch origin
161 git reset --hard origin/asf-site
{quote}

yeah, we were doing it at the end but we do a fresh clone every run.

{quote}
Is this meant to be commented out?

275 #if git push origin asf-site; then
{quote}

That's been commented out to ensure I don't push to the remote. I'll make it 
not commented out before pushing. I can update the patch with that change in 
place if folks prefer.

> 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
(v7.6.3#76005)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-02 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

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

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

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-01 Thread stack (JIRA)


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

stack commented on HBASE-20070:
---

TestProcedurePriority has failed a few times. Has nought to do w/ site 
generation.

Maybe I don't need to wait on this patch for beta-2 afterall... will see.

Looking at patch...

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

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

Nice usage function.

none in general properties gets picked up by javadoc? Thats 
good.

This was just noise?

168 #echo "Dumping current environment:"
169 #env

...and this unnecessary work?

160   git fetch origin  
161   git reset --hard origin/asf-site

Is this meant to be commented out?

275   #if git push origin asf-site; then

Patch looks great.





> 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
(v7.6.3#76005)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-01 Thread stack (JIRA)


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

stack commented on HBASE-20070:
---

+1 on commit to branch-2 now.  Need it to make rc iiuc.  Thanks.

> 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
(v7.6.3#76005)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-01 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on HBASE-20070:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
22s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
3s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
17s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  5m  
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
19s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 10m 
18s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue}  0m 
12s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  4m 
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  4m 
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 0s{color} | {color:green} The patch generated 0 new + 0 unchanged - 1 fixed = 
0 total (was 1) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green}  0m 
48s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  5m 
49s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
19m 36s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  9m  
8s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}121m  4s{color} 
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  9m 
30s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}197m 57s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.master.procedure.TestProcedurePriority |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20070 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12912630/HBASE-20070.6.patch |
| Optional Tests |  asflicense  shellcheck  shelldocs  javac  javadoc  unit  
shadedjars  hadoopcheck  xml  compile  |
| uname | Linux 17b227e8ab73 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9 
14:43:09 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
 |
| git revision | master / e86ffedb45 |
| maven | version: Apache Maven 3.5.2 
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_151 |
| shellcheck | v0.4.4 |
| unit | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11748/artifact/patchprocess/patch-unit-root.txt
 |
|  Test Results |

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-01 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

-6

  - 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
(v7.6.3#76005)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-03-01 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

oh found it! it's the git diff.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

what's your maven and git versions?

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on HBASE-20070:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
9s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} shelldocs {color} | {color:blue}  0m  
3s{color} | {color:blue} Shelldocs was not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green}  0m  
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red}  0m  
0s{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  5m 
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  6m 
 0s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  4m 
29s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  4m 
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  4m 
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green}  0m 
 0s{color} | {color:green} The patch generated 0 new + 0 unchanged - 1 fixed = 
0 total (was 1) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green}  0m 
 0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green}  0m  
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
46s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
19m 12s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  4m 
27s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}148m  6s{color} 
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
31s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}203m 26s{color} | 
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestBlockEvictionFromClient |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:eee3b01 |
| JIRA Issue | HBASE-20070 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12912509/HBASE-20070.5.patch |
| Optional Tests |  asflicense  shellcheck  shelldocs  javac  javadoc  unit  
shadedjars  hadoopcheck  xml  compile  |
| uname | Linux 2d676dfd98e4 3.13.0-133-generic #182-Ubuntu SMP Tue Sep 19 
15:49:21 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / bdedcc5631 |
| maven | version: Apache Maven 3.5.2 
(138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) |
| Default Java | 1.8.0_151 |
| shellcheck | v0.4.4 |
| unit | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11734/artifact/patchprocess/patch-unit-root.txt
 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11734/testReport/ |
| Max. process+thread count | 4073 (vs. ulimit of 1) |
| modules | C: . U: . |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11734/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

Actually soft -1 on version 5. I forgot to mention that there is something 
about the way you are adding files to git that is making it interactive (you 
have to press {{q}} to get out of a pager). I didn't look into it to see what 
the deal is but probably not appropriate for a Jenkins job.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

+1 on version 5.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

-5
  - update use of cp to use flags that also work on mac.

I updated cp to use {{-pPR}}, which should be "recursively copy everything 
while maintaining file metadata (owner, timestamp, access)" on both Mac 
(10.11.6 built-in tested) and Linux (CentOS 7.4 tested).

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

Testing latest patch now.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

FYI with that one change, I got a totally clean run of all phases including 
adding the files, generating the patch, etc. I can't reproduce the dependency 
problem you were seeing.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

You might be using {{cp}} from Homebrew. If it is in {{/usr/local/bin}} that's 
probably what's going on. Yes, that's the line. I'm pretty sure that Linux 
{{cp}} supporting {{-r}} is new so it is possible Jenkins won't work with this, 
in which case you'll have to somehow check what flags are supported or just use 
{{mv}} or something (even {{rsync}} but that's more complicated).

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

Just to confirm, this is the line I'm updating, right?

{code}
cp -au "${component_dir}"/target/staging/* .
{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-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

curious. I'm using a mac locally, so I wonder why this didn't fail for me.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-28 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

-1 on patch 4, because it won't run on Mac out of the box, due to differences 
in the {{cp}} command. I solved a similar thing with sed here: 
[https://github.com/docker/docker.github.io/blob/master/_scripts/fetch-upstream-resources.sh#L10]

 

However it looks like Linux honors the {{-r}} flag for {{cp}} now, so maybe you 
can just switch the {{-au}} to {{-r}} everywhere (after verifying on a Jenkins 
worker that it has a version of {{cp}} that supports the flag?)

 

I've changed the {{cp}} locally and will do more testing today.

 

(I sent this hours ago but it didn't post because the session was expired but 
the page doesn't have the smarts to realize that.)

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-27 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

I probably won't have time to keep digging on this today. I'll pick it back up 
again later this week.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-27 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

-4
  - make the version of maven-javadoc-plugin consistently 3.0.0 and update how 
we turn off the javadoc linter.

After this addition I still get a failure, but now it's a weird dependency 
resolution thing instead of a javadoc complaint.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

Also, MJAVADOC-511 is interesting as a way we might have been spared some pain 
here.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

-3
  - starts forcing {{-e}} instead of relying on how the script is called
  - adds command line arg parsing, including optional working directory, local 
repo, and publishing
  - creates a working directory in {{/tmp}} if one isn't given

Note that invoking the script is totally different now:

{code}
 bash hbase/dev-support/jenkins-scripts/generate-hbase-website.sh --help
Usage: hbase/dev-support/jenkins-scripts/generate-hbase-website.sh [options] 
/path/to/hbase/checkout

--working-dir /path/to/use  Path for writing logs and a local checkout of 
hbase-site repo.
if given must exist.
defaults to making a directory in /tmp.
--local-repo /path/for/maven/.m2  Path for putting local maven repo.
if given must exist.
defaults to making a clean directory in 
--working-dir.
--publish   if given, will attempt to push results back to 
the hbase-site repo.
--help  show this usage message.
{code}

Also note that even if you pass in the {{--publish}} flag, the actual push to 
git is still commented out.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

No, adding the configuration to the reportsets in the POM didn't help either. 
:/ I am confused, but need to step away from this for a bit. I'll attach my 
patch as it currently stands, for your review. I didn't try to normalize to 
your patch yet, so ignore any changes you incorporated already.

> 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.0.patch, HBASE-20070.1.patch, HBASE-20070.2.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

I'm confused why the Javadoc is failing even with this in the POM:

 
{code:java}


-Xdoclint:none
{code}
I found that referred to at 
[http://www.locked.de/2015/04/05/how-to-ignore-maven-javadoc-errors-in-java-8/.|http://www.locked.de/2015/04/05/how-to-ignore-maven-javadoc-errors-in-java-8/]

 

But I think that maybe the configuration clause is actually in the wrong place 
in the POM. I'm testing this assumption now.

> 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.0.patch, HBASE-20070.1.patch, HBASE-20070.2.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

I think maybe we aren't supposed to be doing {{mvn clean site}} after doing the 
install? Maybe just {{mvn site}}. This might be the cause of the Javadoc errors 
you're seeing. I'm testing locally now.

> 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.0.patch, HBASE-20070.1.patch, HBASE-20070.2.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

{quote}
I think this might not be quite right (mine was also probably wrong). If I am 
understanding this correctly, this will pass if the hash is in any branch we 
know about, not just `master`, but I think we only care if it is in `master`. 
Can we narrow it down more? I'm also not in love with this indent-less syntax 
for the if contents.
{quote}

the git command that counted things for PUSHED only traces back commits 
starting from some reference (in this case the local HEAD), so it should only 
count things in the {{asf-site}} branch of the hbase-site repo. Which I think 
is correct?

The {{if}} block in my patch should be indented two spaces. It is when I open 
things in vim at least. 

{quote}
I think we need to document that the stuff that removes ~/.m2 may not work 
locally but that's specifically to try to avoid Jenkins server problems so it 
can probably be ignored locally. In fact maybe there is some cleverer way for 
us to sandbox ourselves, but I am not a Maven expert.
{quote}

If {{WORKSPACE}} exists, then the temp directory should work. We could move it 
out of this script though, and just have folks pass in a path for what they 
want used for the maven local repository. we could then manage the 
per-workspace repository via jenkins. better?

{quote}
I think maybe we need to add a –push=true or similar flag to this script so we 
can do local tests without it always pushing the new site.
{quote}

Sure. I've been commenting out the push while I have a WIP. I can add a flag 
for publishing.

> 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.0.patch, HBASE-20070.1.patch, HBASE-20070.2.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

A little bit of feedback on your patches so far. Some of this may be me not 
understanding certain ways of doing things in Bash, so forgive me if so.

 
{code:java}
if [ "${PUSHED}" -ne 0 ]; then
echo "$CURRENT_HBASE_COMMIT is already mentioned in the hbase-site commit log. 
Not building."
exit 0
else{code}
I think this might not be quite right (mine was also probably wrong). If I am 
understanding this correctly, this will pass if the hash is in any branch we 
know about, not just `master`, but I think we only care if it is in `master`. 
Can we narrow it down more? I'm also not in love with this indent-less syntax 
for the if contents.

 

I think we need to document that the stuff that removes {{~/.m2}} may not work 
locally but that's specifically to try to avoid Jenkins server problems so it 
can probably be ignored locally. In fact maybe there is some cleverer way for 
us to sandbox ourselves, but I am not a Maven expert.

 

I think maybe we need to add a {{–push=true}} or similar flag to this script so 
we can do local tests without it always pushing the new site.

 

 

 

 

> 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.0.patch, HBASE-20070.1.patch, HBASE-20070.2.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

-2
  - added docs on assumptions based on chatting with Misty
  - avoids messing with JAVA_HOME and MAVEN_HOME if they exist

The way the script tried to set JAVA_HOME was effectively unsetting it on my 
machine, which meant I got jdk9 which didn't work.

still getting an error on running site, it looks like from trying to make 
javadocs.

> 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.0.patch, HBASE-20070.1.patch, HBASE-20070.2.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

maybe the site failure is HBASE-15753?

> 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.0.patch, HBASE-20070.1.patch, HBASE-20070.2.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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

Yeah it is still needed because that is stuff that is actually checked in but 
we want to nuke and pave it.

> 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.0.patch, HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

{code:java}
> index 06d160a64c..4628697c5f 100644
36c40
< +if [ -z "$CURRENT_HBASE_COMMIT "]; then
---
> +if [ -z "$CURRENT_HBASE_COMMIT" ]; then
55c59
< +PUSHED=$(git log -pretty=%H | grep ${CURRENT_HBASE_COMMIT})
---
> +PUSHED=$(git log --pretty=%H | grep ${CURRENT_HBASE_COMMIT}){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.0.patch, HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

{code}
#Remove previously-generated files
FILES_TO_REMOVE=("hbase-*"
 "apidocs"
 "devapidocs"
 "testapidocs"
 "testdevapidocs"
 "xref"
 "xref-test"
 "*book*"
 "*.html"
 "*.pdf*"
 "css"
 "js"
 "images")

for FILE in "${FILES_TO_REMOVE[@]}"; do
  if [ -e "${FILE}" ]; then
echo "Removing ${WORKSPACE}/hbase-site/$FILE"
rm -Rf "${FILE}"
  fi
done
{code}

Do you think this stanza is actually needed? Don't we delete the hbase-site 
directory and do a fresh clone on each run?

> 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.0.patch, HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

bq.  Attached another version of mine with a couple fixes I noticed in testing.

I'm trying to incorporate things before uploading my current patch. could you 
summarize the difference from your previous patch? I'm not seeing it. 
(downloading the first one again now to diff)

> 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.0.patch, HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

Attached another version of mine with a couple fixes I noticed in testing.

> 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.0.patch, HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

oh wait! it might just be because my local jdk defaults to jdk9. let me confirm 
or deny that.

> 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.0.patch, 
> HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

bq. I think that build failure is unrelated and probably a `git bisect` is 
needed to see who broke it.

Okay, let me make a different jira for that. Should a passing {{mvn site}} be a 
blocker for this change to the jenkins script?

> 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.0.patch, 
> HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

I think that build failure is unrelated and probably a `git bisect` is needed 
to see who broke it.

> 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.0.patch, 
> HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

Read through the {{HBASE-20070.misty.patch}} and it looks pretty similar to 
what I already have posted. It's still ignoring when commands fail unless 
they're expressly checked for, which I'd really like to avoid.

{code}
+PUSHED=$(git log -pretty=%H | grep ${CURRENT_HBASE_COMMIT})
{code}

this is still relying on the format string and then matching output when all we 
need to know is if a commit exists. why go through the extra work?

> 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.0.patch, 
> HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

I don't think you can do absolutely everything with plumbing commands. Not 100% 
sure though.

> 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.0.patch, 
> HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

{quote}I'll look at your patch if you look at mine. {quote}

sure.

Things still relying on git porcelain commands: clone, commit, push. I don't 
know how to do those via plumbing and couldn't figure it out with ~5 minutes of 
checking. so I'd like to leave it as follow-on work.

> 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.0.patch, 
> HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

I'll look at your patch if you look at mine. :)

> 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.0.patch, 
> HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

-1
  - fixes a missing set of quotes that got flagged by shellcheck

> 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.0.patch, HBASE-20070.1.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

I get to the point of building the site and then it fails. attaching the log. I 
think it's unrelated to this git problem, so should have a new JIRA, WDYT 
[~misty]?

> 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.0.patch, 
> hbase-build-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)

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

let me post my WIP patch while the build runs locally then.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Misty Stanley-Jones (JIRA)


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

Misty Stanley-Jones commented on HBASE-20070:
-

I'm taking a look now.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

correction to my original description, we should be using git plumbing 
commands, not porcelain. plumbing are the ones for scripts that don't change 
often.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-26 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

getting the current commit hash has bean failing since August, but it seems it 
was failing in a way that still updated the website.

patch shortly.

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

[jira] [Commented] (HBASE-20070) website generation is failing

2018-02-24 Thread Sean Busbey (JIRA)


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

Sean Busbey commented on HBASE-20070:
-

the git porcelain command for "tell me the full commit hash for the current 
working directory and error out if something goes wrong" is {{git rev-parse 
--verify HEAD}}.

alternatively we could expressly make this {{git rev-parse --verify 
origin/master}} if we wanted to guard against there being a local commit, or 
{{git rev-parse --verify origin/HEAD}} if we wanted to future proof against us 
deciding that our "place new stuff and docs lands first" should be something 
other than master. 

> 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
>Priority: Blocker
>
> 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)

66 matches

Mail list logo