subject:"Failure\: HBase Generate Website"

Failure: HBase Generate Website

2024-04-21 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See https://ci-hbase.apache.org/job/hbase_generate_website/516/console

Failure: HBase Generate Website

2024-03-19 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See https://ci-hbase.apache.org/job/hbase_generate_website/496/console

Failure: HBase Generate Website

2024-03-18 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See https://ci-hbase.apache.org/job/hbase_generate_website/495/console

Failure: HBase Generate Website

2022-01-29 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/439/console

Failure: HBase Generate Website

2022-01-19 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/431/console

Failure: HBase Generate Website

2022-01-07 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/423/console

Failure: HBase Generate Website

2022-01-05 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/420/console

Failure: HBase Generate Website

2021-12-05 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/395/console

Failure: HBase Generate Website

2021-12-04 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/394/console

Failure: HBase Generate Website

2021-11-07 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/375/console

Failure: HBase Generate Website

2021-06-30 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/281/console

Failure: HBase Generate Website

2021-06-05 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/259/console

Failure: HBase Generate Website

2021-04-26 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/224/console

Failure: HBase Generate Website

2021-03-18 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/193/console

Failure: HBase Generate Website

2021-01-26 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/152/console

Failure: HBase Generate Website

2021-01-05 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See 
https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/135/console

Re: Failure: HBase Generate Website

2020-11-12 Thread Peter Somogyi

I have a Pull Request to fix the website build waiting for reviews.
https://issues.apache.org/jira/browse/HBASE-25275

On Wed, Nov 11, 2020 at 9:18 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

>
> Build status: FAILURE
>
> The HBase website has not been updated to incorporate recent HBase changes.
>
> See
> https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/90/console
>

Failure: HBase Generate Website

2020-11-11 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/90/console

Failure: HBase Generate Website

2020-11-10 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/89/console

Re: Failure: HBase Generate Website

2020-08-11 Thread Sean Busbey

this is a side effect of HBASE-24869. feel free to ignore.

On 2020/08/12 05:16:42, Apache Jenkins Server   
wrote: 
> 
> Build status: FAILURE
> 
> The HBase website has not been updated to incorporate recent HBase changes.
> 
> See 
> https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/6/console
>

Failure: HBase Generate Website

2020-08-11 Thread Apache Jenkins Server


Build status: FAILURE

The HBase website has not been updated to incorporate recent HBase changes.

See https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/6/console

Failure: HBase Generate Website

2020-05-22 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/2016/console

Failure: HBase Generate Website

2020-01-27 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1907/console

Re: Failure: HBase Generate Website

2019-09-03 Thread Nick Dimiduk

Thanks for checking.

On Tue, Sep 3, 2019 at 08:11 Josh Elser  wrote:

> In case someone else was meaning to look at this:
>
> Seems to be transient. status.a.o doesn't go back far enough to see if
> this was an acknowledged issue.
>
> 
> Connect to repository.apache.org:80
> [repository.apache.org/207.244.88.140] failed: Connection timed out
> (Connection timed out)
> 
>
> 4 green builds since then.
>
> On 8/31/19 10:45 AM, Apache Jenkins Server wrote:
> > Build status: Failure
> >
> > The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> >
> > See https://builds.apache.org/job/hbase_generate_website/1775/console
> >
>

Re: Failure: HBase Generate Website

2019-09-03 Thread Josh Elser


In case someone else was meaning to look at this:

Seems to be transient. status.a.o doesn't go back far enough to see if 
this was an acknowledged issue.



Connect to repository.apache.org:80 
[repository.apache.org/207.244.88.140] failed: Connection timed out 
(Connection timed out)



4 green builds since then.

On 8/31/19 10:45 AM, Apache Jenkins Server wrote:

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1775/console

Failure: HBase Generate Website

2019-08-31 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1775/console

Re: Failure: HBase Generate Website

2019-06-03 Thread Sean Busbey

yep. I filed an infra jira:

https://issues.apache.org/jira/browse/INFRA-18557

On Mon, Jun 3, 2019 at 7:01 AM 张铎(Duo Zhang)  wrote:
>
> Seems out of disk space?
>
> Apache Jenkins Server 于2019年6月3日 周一19:58写道：
>
> > Build status: Failure
> >
> > The HBase website has not been updated to incorporate HBase commit
> > ${CURRENT_HBASE_COMMIT}.
> >
> > See https://builds.apache.org/job/hbase_generate_website/1696/console



-- 
Sean

Re: Failure: HBase Generate Website

2019-06-03 Thread Duo Zhang

Seems out of disk space?

Apache Jenkins Server 于2019年6月3日 周一19:58写道：

> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1696/console

Failure: HBase Generate Website

2019-06-03 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1696/console

Failure: HBase Generate Website

2019-06-01 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1693/console

Failure: HBase Generate Website

2019-05-04 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1666/console

Failure: HBase Generate Website

2019-04-10 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1641/console

Re: Failure: HBase Generate Website

2019-03-26 Thread Peter Somogyi

Issue is fixed and the new job succeeded.

On Tue, Mar 26, 2019 at 3:34 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1627/console

Failure: HBase Generate Website

2019-03-26 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1627/console

Re: Failure: HBase Generate Website

2019-03-07 Thread Sean Busbey

okay this is fixed now thanks to an addendum on HBASE-21999.

https://builds.apache.org/job/hbase_generate_website/1611/

On Thu, Mar 7, 2019 at 10:29 AM Peter Somogyi  wrote:
>
> Yes, git version is 2.7.4 which does not support --no-show-signature.
>
> On Thu, Mar 7, 2019 at 5:27 PM Sean Busbey  wrote:
>
> > ah, by "malformed" I of course mean missing entirely. yeah this is a
> > result of HBASE-21999. since we exit before creating the Version class
> > definition at all when the git revision is blank. We must have been
> > creating an hbase build with unknown revisions for some time.
> >
> >
> >
> > On Thu, Mar 7, 2019 at 10:20 AM Sean Busbey  wrote:
> > >
> > > Building is failing because the generated Version class is malformed.
> > >
> > > Looking at the changeset, maybe HBASE-21999 is to blame?
> > >
> > > On Thu, Mar 7, 2019 at 8:31 AM Apache Jenkins Server
> > >  wrote:
> > > >
> > > > Build status: Failure
> > > >
> > > > The HBase website has not been updated to incorporate HBase commit
> > ${CURRENT_HBASE_COMMIT}.
> > > >
> > > > See https://builds.apache.org/job/hbase_generate_website/1610/console
> >



-- 
Sean

Re: Failure: HBase Generate Website

2019-03-07 Thread Peter Somogyi

Yes, git version is 2.7.4 which does not support --no-show-signature.

On Thu, Mar 7, 2019 at 5:27 PM Sean Busbey  wrote:

> ah, by "malformed" I of course mean missing entirely. yeah this is a
> result of HBASE-21999. since we exit before creating the Version class
> definition at all when the git revision is blank. We must have been
> creating an hbase build with unknown revisions for some time.
>
>
>
> On Thu, Mar 7, 2019 at 10:20 AM Sean Busbey  wrote:
> >
> > Building is failing because the generated Version class is malformed.
> >
> > Looking at the changeset, maybe HBASE-21999 is to blame?
> >
> > On Thu, Mar 7, 2019 at 8:31 AM Apache Jenkins Server
> >  wrote:
> > >
> > > Build status: Failure
> > >
> > > The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> > >
> > > See https://builds.apache.org/job/hbase_generate_website/1610/console
>

Re: Failure: HBase Generate Website

2019-03-07 Thread Sean Busbey

ah, by "malformed" I of course mean missing entirely. yeah this is a
result of HBASE-21999. since we exit before creating the Version class
definition at all when the git revision is blank. We must have been
creating an hbase build with unknown revisions for some time.

On Thu, Mar 7, 2019 at 10:20 AM Sean Busbey  wrote:
>
> Building is failing because the generated Version class is malformed.
>
> Looking at the changeset, maybe HBASE-21999 is to blame?
>
> On Thu, Mar 7, 2019 at 8:31 AM Apache Jenkins Server
>  wrote:
> >
> > Build status: Failure
> >
> > The HBase website has not been updated to incorporate HBase commit 
> > ${CURRENT_HBASE_COMMIT}.
> >
> > See https://builds.apache.org/job/hbase_generate_website/1610/console

Re: Failure: HBase Generate Website

2019-03-07 Thread Sean Busbey

Building is failing because the generated Version class is malformed.

Looking at the changeset, maybe HBASE-21999 is to blame?

On Thu, Mar 7, 2019 at 8:31 AM Apache Jenkins Server
 wrote:
>
> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit 
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1610/console

Failure: HBase Generate Website

2019-03-07 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1610/console

Re: Failure: HBase Generate Website

2019-02-12 Thread Peter Somogyi

A pull request was just merged to hbase-site repo while this build was
running so it failed to push changes. Restarted the job now.

On Tue, Feb 12, 2019 at 3:47 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1585/console

Failure: HBase Generate Website

2019-02-12 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1585/console

Failure: HBase Generate Website

2018-10-05 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1471/console

Failure: HBase Generate Website

2018-08-28 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1439/console

Re: Failure: HBase Generate Website

2018-07-21 Thread Misty Linville

In addition to the build problems probably caused by a lack of Jenkins
workers, there is a bug in the script somewhere that causes the git hash of
the commit that failed to build not to be expanded. I'm not going to be on
a computer all weekend so can someone file and / or investigate?

On Jul 21, 2018 7:30 AM, "Apache Jenkins Server" 
wrote:

Build status: Failure

The HBase website has not been updated to incorporate HBase commit
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1406/console

Failure: HBase Generate Website

2018-07-21 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1406/console

Failure: HBase Generate Website

2018-07-19 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1402/console

Re: Failure: HBase Generate Website

2018-06-11 Thread Ted Yu

Build #1372 passed.

On Mon, Jun 11, 2018 at 7:51 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1371/console

Failure: HBase Generate Website

2018-06-11 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1371/console

Re: Failure: HBase Generate Website

2018-05-27 Thread Peter Somogyi

The connection was lost to the build server. I manually retriggered the job
which succeeded.
https://builds.apache.org/job/hbase_generate_website/1357/

On Sun, May 27, 2018 at 4:43 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1356/console

Failure: HBase Generate Website

2018-05-27 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1356/console

Re: Failure: HBase Generate Website

2018-03-24 Thread Sean Busbey

looks like it was a jenkins flub (worker node disappeared).

Thanks to Peter who ran another job that passed about a half hour afterwards.

On Sat, Mar 24, 2018 at 9:32 AM, Apache Jenkins Server
 wrote:
> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit 
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1294/console

Failure: HBase Generate Website

2018-03-24 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1294/console

Failure: HBase Generate Website

2018-02-22 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1262/console

Failure: HBase Generate Website

2018-02-21 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1260/console

Failure: HBase Generate Website

2017-11-08 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1161/console

Re: Failure: HBase Generate Website

2017-08-10 Thread Misty Stanley-Jones

Spurious. Sorry about that!

On Thu, Aug 10, 2017 at 2:52 PM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See https://builds.apache.org/job/hbase_generate_website/1078/console

Failure: HBase Generate Website

2017-08-10 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${CURRENT_HBASE_COMMIT}.

See https://builds.apache.org/job/hbase_generate_website/1078/console

Failure: HBase Generate Website

2017-08-06 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/1072/console

Failure: HBase Generate Website

2017-07-06 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/1045/console

Re: Failure: HBase Generate Website

2017-07-04 Thread Peter Somogyi

I've created HBASE-18320 
.
The new maven-site-plugin and asciidoctor plugin versions are not
compatible with the currently used site.xml. I've started to work on it. I
think the quickest would be to roll back these plugins to the previous
versions and after we can investigate if we need the new versions or not.

Peter

On Tue, Jul 4, 2017 at 4:40 PM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit
> ${HBASE_GIT_SHA}.
>
> See https://builds.apache.org/job/hbase_generate_website/1043/console

Failure: HBase Generate Website

2017-07-04 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/1043/console

Failure: HBase Generate Website

2017-04-11 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/964/console

Failure: HBase Generate Website

2017-04-11 Thread Apache Jenkins Server

Build status: Failure

The HBase website has not been updated to incorporate HBase commit 
${HBASE_GIT_SHA}.

See https://builds.apache.org/job/hbase_generate_website/955/console

Failure: HBase Generate Website

2017-04-10 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated and the site has been 
updated automatically.
If you're getting this email, it probably failed and you may need to update the 
site manually if you can't get Jenkins fixed.

If failed, see https://builds.apache.org/job/hbase_generate_website/952/console

YOU DO NOT NEED TO DO THE FOLLOWING ANYMORE! It is here for informational 
purposes and shows what the Jenkins job does to push the site.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/952/artifact/website.patch.zip
 | funzip > 82d554e3783372cc6b05489452c815b57c06f6cd.patch
  git fetch
  git checkout -b asf-site-82d554e3783372cc6b05489452c815b57c06f6cd 
origin/asf-site
  git am --whitespace=fix 82d554e3783372cc6b05489452c815b57c06f6cd.patch
  git push origin asf-site-82d554e3783372cc6b05489452c815b57c06f6cd:asf-site
  git commit --allow-empty -m "INFRA-10751 Empty commit"
  git push origin asf-site
  git checkout asf-site
  git branch -D asf-site-82d554e3783372cc6b05489452c815b57c06f6cd

Failure: HBase Generate Website

2017-04-06 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated and the site has been 
updated automatically.
If you're getting this email, it probably failed and you may need to update the 
site manually if you can't get Jenkins fixed.

If failed, see https://builds.apache.org/job/hbase_generate_website/801/console

YOU DO NOT NEED TO DO THE FOLLOWING ANYMORE! It is here for informational 
purposes and shows what the Jenkins job does to push the site.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/801/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch
  git push origin asf-site-${GIT_SHA}:asf-site
  git commit --allow-empty -m "INFRA-10751 Empty commit"
  git push origin asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Failure: HBase Generate Website

2017-03-24 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/538/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/538/console

Re: Failure: HBase Generate Website

2017-03-22 Thread Dima Spivak

Not actually a problem with the site; looks like the Jenkins slave shutdown
during the build.

-Dima

On Wed, Mar 22, 2017 at 12:46 PM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O- https://builds.apache.org/job/hbase_generate_website/535/art
> ifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see https://builds.apache.org/job/
> hbase_generate_website/535/console

Failure: HBase Generate Website

2017-03-22 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/535/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/535/console

Re: Failure: HBase Generate Website

2017-03-20 Thread Stack

Yes. My fault. Thanks for the kick Dima.
St.Ack

On Mon, Mar 20, 2017 at 1:52 PM, Dima Spivak  wrote:

> Looks like we have a hanging tag on the resources page, Stack. Can you take
> a look?
>
> On Mon, Mar 20, 2017 at 12:13 PM Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> Build status: Failure
>
> If successful, the website and docs have been generated. To update the live
> site, follow the instructions below. If failed, skip to the bottom of this
> email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O-
> https://builds.apache.org/job/hbase_generate_website/525/
> artifact/website.patch.zip
> | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using these
> commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current ASF
> INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/525/console
>
> --
> -Dima
>

Re: Failure: HBase Generate Website

2017-03-20 Thread Dima Spivak

Looks like we have a hanging tag on the resources page, Stack. Can you take
a look?

On Mon, Mar 20, 2017 at 12:13 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

Build status: Failure

If successful, the website and docs have been generated. To update the live
site, follow the instructions below. If failed, skip to the bottom of this
email.

Use the following commands to download the patch and apply it to a clean
branch based on origin/asf-site. If you prefer to keep the hbase-site repo
around permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O-
https://builds.apache.org/job/hbase_generate_website/525/artifact/website.patch.zip
| funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of
the other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in
tables, so a generic git diff is not very useful. To see a list of files
that have been added, deleted, renamed, changed type, or are otherwise
interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether
they have been propagated by looking at the Last Published date at the
bottom of http://hbase.apache.org/. It should match the date in the
index.html on the asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you
pushed the site.



If failed, see
https://builds.apache.org/job/hbase_generate_website/525/console

-- 
-Dima

Failure: HBase Generate Website

2017-03-20 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/525/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/525/console

Failure: HBase Generate Website

2017-02-18 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/492/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/492/console

Failure: HBase Generate Website

2016-11-21 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/412/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/412/console

Re: Failure: HBase Generate Website

2016-10-27 Thread Ted Yu

I applied addendum and ran a few unit tests which passed.

FYI

On Thu, Oct 27, 2016 at 8:44 AM, Ted Yu  wrote:

> It turns out that HBASE-16932 moved the definition of MAX_BYTE_ARRAY :
>
> git show cd3dd6e018513357d2cf0b5bba073f5a6551f7a4
> ./hbase-client/src/main/java/org/apache/hadoop/hbase/
> client/ClientScanner.java
>
> -static byte[] MAX_BYTE_ARRAY = Bytes.createMaxByteArray(9);
>
> On Thu, Oct 27, 2016 at 8:10 AM, Andrew Purtell 
> wrote:
>
>> I checked the last QA report on this issue and, while the findbugs and
>> unit test results were red, there was nothing that would indicate the site
>> build would fail.
>>
>> Am I missing something?
>>
>> Is the only way we will know if a change will break the site build is to
>> run a site build before every check in?
>>
>> If so, that won't work out well. Can we add a site check to precommit?
>>
>> > On Oct 27, 2016, at 10:54 AM, Dima Spivak 
>> wrote:
>> >
>> > HBASE-16886 breaks compilation. Ted, please revert.
>> >
>> > On Thursday, October 27, 2016, Apache Jenkins Server <
>> > jenk...@builds.apache.org> wrote:
>> >
>> >> Build status: Failure
>> >>
>> >> If successful, the website and docs have been generated. To update the
>> >> live site, follow the instructions below. If failed, skip to the
>> bottom of
>> >> this email.
>> >>
>> >> Use the following commands to download the patch and apply it to a
>> clean
>> >> branch based on origin/asf-site. If you prefer to keep the hbase-site
>> repo
>> >> around permanently, you can skip the clone step.
>> >>
>> >>  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>> >>
>> >>  cd hbase-site
>> >>  wget -O- https://builds.apache.org/job/hbase_generate_website/390/
>> >> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>> >>  git fetch
>> >>  git checkout -b asf-site-${GIT_SHA} origin/asf-site
>> >>  git am --whitespace=fix $GIT_SHA.patch
>> >>
>> >> At this point, you can preview the changes by opening index.html or
>> any of
>> >> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>> >>
>> >> There are lots of spurious changes, such as timestamps and CSS styles
>> in
>> >> tables, so a generic git diff is not very useful. To see a list of
>> files
>> >> that have been added, deleted, renamed, changed type, or are otherwise
>> >> interesting, use the following command:
>> >>
>> >>  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>> >>
>> >> To see only files that had 100 or more lines changed:
>> >>
>> >>  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>> >>
>> >> When you are satisfied, publish your changes to origin/asf-site using
>> >> these commands:
>> >>
>> >>  git commit --allow-empty -m "Empty commit" # to work around a current
>> >> ASF INFRA bug
>> >>  git push origin asf-site-${GIT_SHA}:asf-site
>> >>  git checkout asf-site
>> >>  git branch -D asf-site-${GIT_SHA}
>> >>
>> >> Changes take a couple of minutes to be propagated. You can verify
>> whether
>> >> they have been propagated by looking at the Last Published date at the
>> >> bottom of http://hbase.apache.org/. It should match the date in the
>> >> index.html on the asf-site branch in Git.
>> >>
>> >> As a courtesy- reply-all to this email to let other committers know you
>> >> pushed the site.
>> >>
>> >>
>> >>
>> >> If failed, see https://builds.apache.org/job/
>> hbase_generate_website/390/
>> >> console
>> >
>> >
>> >
>> > --
>> > -Dima
>>
>
>

Re: Failure: HBase Generate Website

2016-10-27 Thread Ted Yu

It turns out that HBASE-16932 moved the definition of MAX_BYTE_ARRAY :

git show cd3dd6e018513357d2cf0b5bba073f5a6551f7a4
./hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java

-static byte[] MAX_BYTE_ARRAY = Bytes.createMaxByteArray(9);

On Thu, Oct 27, 2016 at 8:10 AM, Andrew Purtell 
wrote:

> I checked the last QA report on this issue and, while the findbugs and
> unit test results were red, there was nothing that would indicate the site
> build would fail.
>
> Am I missing something?
>
> Is the only way we will know if a change will break the site build is to
> run a site build before every check in?
>
> If so, that won't work out well. Can we add a site check to precommit?
>
> > On Oct 27, 2016, at 10:54 AM, Dima Spivak  wrote:
> >
> > HBASE-16886 breaks compilation. Ted, please revert.
> >
> > On Thursday, October 27, 2016, Apache Jenkins Server <
> > jenk...@builds.apache.org> wrote:
> >
> >> Build status: Failure
> >>
> >> If successful, the website and docs have been generated. To update the
> >> live site, follow the instructions below. If failed, skip to the bottom
> of
> >> this email.
> >>
> >> Use the following commands to download the patch and apply it to a clean
> >> branch based on origin/asf-site. If you prefer to keep the hbase-site
> repo
> >> around permanently, you can skip the clone step.
> >>
> >>  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >>
> >>  cd hbase-site
> >>  wget -O- https://builds.apache.org/job/hbase_generate_website/390/
> >> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> >>  git fetch
> >>  git checkout -b asf-site-${GIT_SHA} origin/asf-site
> >>  git am --whitespace=fix $GIT_SHA.patch
> >>
> >> At this point, you can preview the changes by opening index.html or any
> of
> >> the other HTML pages in your local asf-site-${GIT_SHA} branch.
> >>
> >> There are lots of spurious changes, such as timestamps and CSS styles in
> >> tables, so a generic git diff is not very useful. To see a list of files
> >> that have been added, deleted, renamed, changed type, or are otherwise
> >> interesting, use the following command:
> >>
> >>  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >>
> >> To see only files that had 100 or more lines changed:
> >>
> >>  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >>
> >> When you are satisfied, publish your changes to origin/asf-site using
> >> these commands:
> >>
> >>  git commit --allow-empty -m "Empty commit" # to work around a current
> >> ASF INFRA bug
> >>  git push origin asf-site-${GIT_SHA}:asf-site
> >>  git checkout asf-site
> >>  git branch -D asf-site-${GIT_SHA}
> >>
> >> Changes take a couple of minutes to be propagated. You can verify
> whether
> >> they have been propagated by looking at the Last Published date at the
> >> bottom of http://hbase.apache.org/. It should match the date in the
> >> index.html on the asf-site branch in Git.
> >>
> >> As a courtesy- reply-all to this email to let other committers know you
> >> pushed the site.
> >>
> >>
> >>
> >> If failed, see https://builds.apache.org/job/
> hbase_generate_website/390/
> >> console
> >
> >
> >
> > --
> > -Dima
>

Re: Failure: HBase Generate Website

2016-10-27 Thread Dima Spivak

The change actually breaks compilation of the hbase-client module. Really
puzzled by why Yetus didn't have an issue with it yesterday...

On Thursday, October 27, 2016, Andrew Purtell 
wrote:

> I checked the last QA report on this issue and, while the findbugs and
> unit test results were red, there was nothing that would indicate the site
> build would fail.
>
> Am I missing something?
>
> Is the only way we will know if a change will break the site build is to
> run a site build before every check in?
>
> If so, that won't work out well. Can we add a site check to precommit?
>
> > On Oct 27, 2016, at 10:54 AM, Dima Spivak  > wrote:
> >
> > HBASE-16886 breaks compilation. Ted, please revert.
> >
> > On Thursday, October 27, 2016, Apache Jenkins Server <
> > jenk...@builds.apache.org > wrote:
> >
> >> Build status: Failure
> >>
> >> If successful, the website and docs have been generated. To update the
> >> live site, follow the instructions below. If failed, skip to the bottom
> of
> >> this email.
> >>
> >> Use the following commands to download the patch and apply it to a clean
> >> branch based on origin/asf-site. If you prefer to keep the hbase-site
> repo
> >> around permanently, you can skip the clone step.
> >>
> >>  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >>
> >>  cd hbase-site
> >>  wget -O- https://builds.apache.org/job/hbase_generate_website/390/
> >> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> >>  git fetch
> >>  git checkout -b asf-site-${GIT_SHA} origin/asf-site
> >>  git am --whitespace=fix $GIT_SHA.patch
> >>
> >> At this point, you can preview the changes by opening index.html or any
> of
> >> the other HTML pages in your local asf-site-${GIT_SHA} branch.
> >>
> >> There are lots of spurious changes, such as timestamps and CSS styles in
> >> tables, so a generic git diff is not very useful. To see a list of files
> >> that have been added, deleted, renamed, changed type, or are otherwise
> >> interesting, use the following command:
> >>
> >>  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >>
> >> To see only files that had 100 or more lines changed:
> >>
> >>  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >>
> >> When you are satisfied, publish your changes to origin/asf-site using
> >> these commands:
> >>
> >>  git commit --allow-empty -m "Empty commit" # to work around a current
> >> ASF INFRA bug
> >>  git push origin asf-site-${GIT_SHA}:asf-site
> >>  git checkout asf-site
> >>  git branch -D asf-site-${GIT_SHA}
> >>
> >> Changes take a couple of minutes to be propagated. You can verify
> whether
> >> they have been propagated by looking at the Last Published date at the
> >> bottom of http://hbase.apache.org/. It should match the date in the
> >> index.html on the asf-site branch in Git.
> >>
> >> As a courtesy- reply-all to this email to let other committers know you
> >> pushed the site.
> >>
> >>
> >>
> >> If failed, see https://builds.apache.org/job/
> hbase_generate_website/390/
> >> console
> >
> >
> >
> > --
> > -Dima
>


-- 
-Dima

Re: Failure: HBase Generate Website

2016-10-27 Thread Andrew Purtell

I checked the last QA report on this issue and, while the findbugs and unit 
test results were red, there was nothing that would indicate the site build 
would fail. 

Am I missing something?

Is the only way we will know if a change will break the site build is to run a 
site build before every check in? 

If so, that won't work out well. Can we add a site check to precommit? 

> On Oct 27, 2016, at 10:54 AM, Dima Spivak  wrote:
> 
> HBASE-16886 breaks compilation. Ted, please revert.
> 
> On Thursday, October 27, 2016, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
> 
>> Build status: Failure
>> 
>> If successful, the website and docs have been generated. To update the
>> live site, follow the instructions below. If failed, skip to the bottom of
>> this email.
>> 
>> Use the following commands to download the patch and apply it to a clean
>> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
>> around permanently, you can skip the clone step.
>> 
>>  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>> 
>>  cd hbase-site
>>  wget -O- https://builds.apache.org/job/hbase_generate_website/390/
>> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>>  git fetch
>>  git checkout -b asf-site-${GIT_SHA} origin/asf-site
>>  git am --whitespace=fix $GIT_SHA.patch
>> 
>> At this point, you can preview the changes by opening index.html or any of
>> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>> 
>> There are lots of spurious changes, such as timestamps and CSS styles in
>> tables, so a generic git diff is not very useful. To see a list of files
>> that have been added, deleted, renamed, changed type, or are otherwise
>> interesting, use the following command:
>> 
>>  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>> 
>> To see only files that had 100 or more lines changed:
>> 
>>  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>> 
>> When you are satisfied, publish your changes to origin/asf-site using
>> these commands:
>> 
>>  git commit --allow-empty -m "Empty commit" # to work around a current
>> ASF INFRA bug
>>  git push origin asf-site-${GIT_SHA}:asf-site
>>  git checkout asf-site
>>  git branch -D asf-site-${GIT_SHA}
>> 
>> Changes take a couple of minutes to be propagated. You can verify whether
>> they have been propagated by looking at the Last Published date at the
>> bottom of http://hbase.apache.org/. It should match the date in the
>> index.html on the asf-site branch in Git.
>> 
>> As a courtesy- reply-all to this email to let other committers know you
>> pushed the site.
>> 
>> 
>> 
>> If failed, see https://builds.apache.org/job/hbase_generate_website/390/
>> console
> 
> 
> 
> -- 
> -Dima

Re: Failure: HBase Generate Website

2016-10-27 Thread Dima Spivak

HBASE-16886 breaks compilation. Ted, please revert.

On Thursday, October 27, 2016, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O- https://builds.apache.org/job/hbase_generate_website/390/
> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see https://builds.apache.org/job/hbase_generate_website/390/
> console



-- 
-Dima

Failure: HBase Generate Website

2016-10-27 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/390/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/390/console

Re: Failure: HBase Generate Website

2016-10-11 Thread Ted Yu

Removed.

On Tue, Oct 11, 2016 at 7:31 AM, Dima Spivak  wrote:

> Why. Ted, please remove this and debug in a separate Jenkins job that won't
> block site generation.
>
> On Tuesday, October 11, 2016, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > Build status: Failure
> >
> > If successful, the website and docs have been generated. To update the
> > live site, follow the instructions below. If failed, skip to the bottom
> of
> > this email.
> >
> > Use the following commands to download the patch and apply it to a clean
> > branch based on origin/asf-site. If you prefer to keep the hbase-site
> repo
> > around permanently, you can skip the clone step.
> >
> >   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >
> >   cd hbase-site
> >   wget -O- https://builds.apache.org/job/hbase_generate_website/374/
> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> >   git fetch
> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> >   git am --whitespace=fix $GIT_SHA.patch
> >
> > At this point, you can preview the changes by opening index.html or any
> of
> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> >
> > There are lots of spurious changes, such as timestamps and CSS styles in
> > tables, so a generic git diff is not very useful. To see a list of files
> > that have been added, deleted, renamed, changed type, or are otherwise
> > interesting, use the following command:
> >
> >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >
> > To see only files that had 100 or more lines changed:
> >
> >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >
> > When you are satisfied, publish your changes to origin/asf-site using
> > these commands:
> >
> >   git commit --allow-empty -m "Empty commit" # to work around a current
> > ASF INFRA bug
> >   git push origin asf-site-${GIT_SHA}:asf-site
> >   git checkout asf-site
> >   git branch -D asf-site-${GIT_SHA}
> >
> > Changes take a couple of minutes to be propagated. You can verify whether
> > they have been propagated by looking at the Last Published date at the
> > bottom of http://hbase.apache.org/. It should match the date in the
> > index.html on the asf-site branch in Git.
> >
> > As a courtesy- reply-all to this email to let other committers know you
> > pushed the site.
> >
> >
> >
> > If failed, see https://builds.apache.org/job/hbase_generate_website/374/
> > console
>
>
>
> --
> -Dima
>

Re: Failure: HBase Generate Website

2016-10-11 Thread Dima Spivak

Why. Ted, please remove this and debug in a separate Jenkins job that won't
block site generation.

On Tuesday, October 11, 2016, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O- https://builds.apache.org/job/hbase_generate_website/374/
> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see https://builds.apache.org/job/hbase_generate_website/374/
> console



-- 
-Dima

Failure: HBase Generate Website

2016-10-11 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/374/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/374/console

Failure: HBase Generate Website

2016-10-10 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/372/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/372/console

Failure: HBase Generate Website

2016-10-07 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/369/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/369/console

Re: Failure: HBase Generate Website

2016-10-04 Thread Dima Spivak

The revert fixed things. Thanks, Ted.

-Dima

On Tue, Oct 4, 2016 at 9:29 AM, Ted Yu  wrote:

> I have reverted the patch.
>
> Will work with Saravanan to get past the error.
>
> FYI
>
> On Tue, Oct 4, 2016 at 8:47 AM, Dima Spivak  wrote:
>
> > Coming so soon after HBASE-16750 got committed worries me. Let me re-run
> > this and revert if it still fails.
> >
> > -Dima
> >
> > On Tue, Oct 4, 2016 at 7:50 AM, Apache Jenkins Server <
> > jenk...@builds.apache.org> wrote:
> >
> > > Build status: Failure
> > >
> > > If successful, the website and docs have been generated. To update the
> > > live site, follow the instructions below. If failed, skip to the bottom
> > of
> > > this email.
> > >
> > > Use the following commands to download the patch and apply it to a
> clean
> > > branch based on origin/asf-site. If you prefer to keep the hbase-site
> > repo
> > > around permanently, you can skip the clone step.
> > >
> > >   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> > >
> > >   cd hbase-site
> > >   wget -O- https://builds.apache.org/job/hbase_generate_website/364/
> > > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> > >   git fetch
> > >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> > >   git am --whitespace=fix $GIT_SHA.patch
> > >
> > > At this point, you can preview the changes by opening index.html or any
> > of
> > > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> > >
> > > There are lots of spurious changes, such as timestamps and CSS styles
> in
> > > tables, so a generic git diff is not very useful. To see a list of
> files
> > > that have been added, deleted, renamed, changed type, or are otherwise
> > > interesting, use the following command:
> > >
> > >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> > >
> > > To see only files that had 100 or more lines changed:
> > >
> > >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> > >
> > > When you are satisfied, publish your changes to origin/asf-site using
> > > these commands:
> > >
> > >   git commit --allow-empty -m "Empty commit" # to work around a current
> > > ASF INFRA bug
> > >   git push origin asf-site-${GIT_SHA}:asf-site
> > >   git checkout asf-site
> > >   git branch -D asf-site-${GIT_SHA}
> > >
> > > Changes take a couple of minutes to be propagated. You can verify
> whether
> > > they have been propagated by looking at the Last Published date at the
> > > bottom of http://hbase.apache.org/. It should match the date in the
> > > index.html on the asf-site branch in Git.
> > >
> > > As a courtesy- reply-all to this email to let other committers know you
> > > pushed the site.
> > >
> > >
> > >
> > > If failed, see https://builds.apache.org/job/
> hbase_generate_website/364/
> > > console
> >
>

Re: Failure: HBase Generate Website

2016-10-04 Thread Ted Yu

I have reverted the patch.

Will work with Saravanan to get past the error.

FYI

On Tue, Oct 4, 2016 at 8:47 AM, Dima Spivak  wrote:

> Coming so soon after HBASE-16750 got committed worries me. Let me re-run
> this and revert if it still fails.
>
> -Dima
>
> On Tue, Oct 4, 2016 at 7:50 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > Build status: Failure
> >
> > If successful, the website and docs have been generated. To update the
> > live site, follow the instructions below. If failed, skip to the bottom
> of
> > this email.
> >
> > Use the following commands to download the patch and apply it to a clean
> > branch based on origin/asf-site. If you prefer to keep the hbase-site
> repo
> > around permanently, you can skip the clone step.
> >
> >   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >
> >   cd hbase-site
> >   wget -O- https://builds.apache.org/job/hbase_generate_website/364/
> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> >   git fetch
> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> >   git am --whitespace=fix $GIT_SHA.patch
> >
> > At this point, you can preview the changes by opening index.html or any
> of
> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> >
> > There are lots of spurious changes, such as timestamps and CSS styles in
> > tables, so a generic git diff is not very useful. To see a list of files
> > that have been added, deleted, renamed, changed type, or are otherwise
> > interesting, use the following command:
> >
> >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >
> > To see only files that had 100 or more lines changed:
> >
> >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >
> > When you are satisfied, publish your changes to origin/asf-site using
> > these commands:
> >
> >   git commit --allow-empty -m "Empty commit" # to work around a current
> > ASF INFRA bug
> >   git push origin asf-site-${GIT_SHA}:asf-site
> >   git checkout asf-site
> >   git branch -D asf-site-${GIT_SHA}
> >
> > Changes take a couple of minutes to be propagated. You can verify whether
> > they have been propagated by looking at the Last Published date at the
> > bottom of http://hbase.apache.org/. It should match the date in the
> > index.html on the asf-site branch in Git.
> >
> > As a courtesy- reply-all to this email to let other committers know you
> > pushed the site.
> >
> >
> >
> > If failed, see https://builds.apache.org/job/hbase_generate_website/364/
> > console
>

Re: Failure: HBase Generate Website

2016-10-04 Thread Dima Spivak

Coming so soon after HBASE-16750 got committed worries me. Let me re-run
this and revert if it still fails.

-Dima

On Tue, Oct 4, 2016 at 7:50 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O- https://builds.apache.org/job/hbase_generate_website/364/
> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see https://builds.apache.org/job/hbase_generate_website/364/
> console

Failure: HBase Generate Website

2016-10-04 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/364/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/364/console

Re: Failure: HBase Generate Website

2016-09-12 Thread 张铎

Ah we also need to use java8 for the jenkins jobs...

Thanks for quick action.

2016-09-12 22:32 GMT+08:00 Dima Spivak :

> Looks like our new Java 8 requirement for master broke this one. I'll fix
> it shortly...
>
> On Monday, September 12, 2016, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
> > Build status: Failure
> >
> > If successful, the website and docs have been generated. To update the
> > live site, follow the instructions below. If failed, skip to the bottom
> of
> > this email.
> >
> > Use the following commands to download the patch and apply it to a clean
> > branch based on origin/asf-site. If you prefer to keep the hbase-site
> repo
> > around permanently, you can skip the clone step.
> >
> >   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >
> >   cd hbase-site
> >   wget -O- https://builds.apache.org/job/hbase_generate_website/340/
> > artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
> >   git fetch
> >   git checkout -b asf-site-${GIT_SHA} origin/asf-site
> >   git am --whitespace=fix $GIT_SHA.patch
> >
> > At this point, you can preview the changes by opening index.html or any
> of
> > the other HTML pages in your local asf-site-${GIT_SHA} branch.
> >
> > There are lots of spurious changes, such as timestamps and CSS styles in
> > tables, so a generic git diff is not very useful. To see a list of files
> > that have been added, deleted, renamed, changed type, or are otherwise
> > interesting, use the following command:
> >
> >   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >
> > To see only files that had 100 or more lines changed:
> >
> >   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >
> > When you are satisfied, publish your changes to origin/asf-site using
> > these commands:
> >
> >   git commit --allow-empty -m "Empty commit" # to work around a current
> > ASF INFRA bug
> >   git push origin asf-site-${GIT_SHA}:asf-site
> >   git checkout asf-site
> >   git branch -D asf-site-${GIT_SHA}
> >
> > Changes take a couple of minutes to be propagated. You can verify whether
> > they have been propagated by looking at the Last Published date at the
> > bottom of http://hbase.apache.org/. It should match the date in the
> > index.html on the asf-site branch in Git.
> >
> > As a courtesy- reply-all to this email to let other committers know you
> > pushed the site.
> >
> >
> >
> > If failed, see https://builds.apache.org/job/hbase_generate_website/340/
> > console
>
>
>
> --
> -Dima
>

Re: Failure: HBase Generate Website

2016-09-12 Thread Dima Spivak

Looks like our new Java 8 requirement for master broke this one. I'll fix
it shortly...

On Monday, September 12, 2016, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O- https://builds.apache.org/job/hbase_generate_website/340/
> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am --whitespace=fix $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-${GIT_SHA}:asf-site
>   git checkout asf-site
>   git branch -D asf-site-${GIT_SHA}
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see https://builds.apache.org/job/hbase_generate_website/340/
> console



-- 
-Dima

Failure: HBase Generate Website

2016-09-12 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/340/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am --whitespace=fix $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-${GIT_SHA}:asf-site
  git checkout asf-site
  git branch -D asf-site-${GIT_SHA}

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/340/console

Failure: HBase Generate Website

2016-04-07 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/191/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-${GIT_SHA}:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-${GIT_SHA} branch:

  git checkout asf-site && git branch -d asf-site-${GIT_SHA}



If failed, see https://builds.apache.org/job/hbase_generate_website/191/console

Re: Failure: HBase Generate Website

2016-03-31 Thread Adrian Muraru

Hi all,

I was wondering, would it make sense to have the the "Documentation and API" 
section of the site maintained for all stable version of HBase and linked form 
hbase.apache.org?
Right now the http://hbase.apache.org/apache_hbase_reference_guide.pdf is 
generated from branch-2.0 AFAICS but sometimes users might want to check the 
reference guide for a specific version.


Thanks,
Adrian

On 3/15/16, 18:51, "Misty Stanley-Jones"  wrote:

>This is HBASE-6721 according to Sean Busbey.
>
>On Tue, Mar 15, 2016 at 8:35 AM, Apache Jenkins Server <
>jenk...@builds.apache.org> wrote:
>
>> Build status: Failure
>>
>> If successful, the website and docs have been generated. If failed, skip
>> to the bottom of this email.
>>
>> Use the following commands to download the patch and apply it to a clean
>> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
>> around permanently, you can skip the clone step.
>>
>>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>>
>>   cd hbase-site
>>   wget -O-
>> https://builds.apache.org/job/hbase_generate_website/166/artifact/website.patch.zip
>> | funzip > ${GIT_SHA}.patch
>>   git fetch
>>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>>   git am $GIT_SHA.patch
>>
>> At this point, you can preview the changes by opening index.html or any of
>> the other HTML pages in your local asf-site-${GIT_SHA} branch, and you can
>> review the differences by running:
>>
>>   git diff origin/asf-site
>>
>> There are lots of spurious changes, such as timestamps and CSS styles in
>> tables. To see a list of files that have been added, deleted, renamed,
>> changed type, or are otherwise interesting, use the following command:
>>
>>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>>
>> To see only files that had 100 or more lines changed:
>>
>>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>>
>> When you are satisfied, publish your changes to origin/asf-site using this
>> command:
>>
>>   git push origin asf-site-${GIT_SHA}:asf-site
>>
>> Changes take a couple of minutes to be propagated. You can then remove
>> your asf-site-${GIT_SHA} branch:
>>
>>   git checkout asf-site && git branch -d asf-site-${GIT_SHA}
>>
>>
>>
>> If failed, see
>> https://builds.apache.org/job/hbase_generate_website/166/console

Failure: HBase Generate Website

2016-03-22 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/174/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-${GIT_SHA}:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-${GIT_SHA} branch:

  git checkout asf-site && git branch -d asf-site-${GIT_SHA}



If failed, see https://builds.apache.org/job/hbase_generate_website/174/console

Re: Failure: HBase Generate Website

2016-03-15 Thread Misty Stanley-Jones

This is HBASE-6721 according to Sean Busbey.

On Tue, Mar 15, 2016 at 8:35 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Failure
>
> If successful, the website and docs have been generated. If failed, skip
> to the bottom of this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O-
> https://builds.apache.org/job/hbase_generate_website/166/artifact/website.patch.zip
> | funzip > ${GIT_SHA}.patch
>   git fetch
>   git checkout -b asf-site-${GIT_SHA} origin/asf-site
>   git am $GIT_SHA.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local asf-site-${GIT_SHA} branch, and you can
> review the differences by running:
>
>   git diff origin/asf-site
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables. To see a list of files that have been added, deleted, renamed,
> changed type, or are otherwise interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using this
> command:
>
>   git push origin asf-site-${GIT_SHA}:asf-site
>
> Changes take a couple of minutes to be propagated. You can then remove
> your asf-site-${GIT_SHA} branch:
>
>   git checkout asf-site && git branch -d asf-site-${GIT_SHA}
>
>
>
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/166/console

Failure: HBase Generate Website

2016-03-15 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/166/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-${GIT_SHA}:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-${GIT_SHA} branch:

  git checkout asf-site && git branch -d asf-site-${GIT_SHA}



If failed, see https://builds.apache.org/job/hbase_generate_website/166/console

Failure: HBase Generate Website

2016-03-09 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/160/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-${GIT_SHA}:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-${GIT_SHA} branch:

  git checkout asf-site && git branch -d asf-site-${GIT_SHA}



If failed, see https://builds.apache.org/job/hbase_generate_website/160/console

Failure: HBase Generate Website

2016-01-20 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/105/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 10 or more lines changed:

  git diff --stat origin/asf-site | grep -Ev "\|\s+\ [1-9]\ [\+-]+$"

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-${GIT_SHA}:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-${GIT_SHA} branch:

  git checkout asf-site && git branch -d asf-site-${GIT_SHA}



If failed, see https://builds.apache.org/job/hbase_generate_website/105/console

Failure: HBase Generate Website

2016-01-05 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/91/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 10 or more lines changed:

  git diff --stat origin/asf-site | grep -Ev "\|\s+\ [1-9]\ [\+-]+$"

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-${GIT_SHA}:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-${GIT_SHA} branch:

  git checkout asf-site && git branch -d asf-site-${GIT_SHA}



If failed, see https://builds.apache.org/job/hbase_generate_website/91/console

Failure: HBase Generate Website

2015-12-07 Thread Apache Jenkins Server

Build status: Failure

If successful, the website and docs have been generated. If failed, skip to the 
bottom of this email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/56/artifact/website.patch.zip
 | funzip > ${GIT_SHA}.patch
  git fetch
  git checkout -b asf-site-${GIT_SHA} origin/asf-site
  git am $GIT_SHA.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local asf-site-${GIT_SHA} branch, and you can review 
the differences by running:

  git diff origin/asf-site

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-${GIT_SHA}:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-${GIT_SHA} branch:

  git checkout asf-site && git branch -d asf-site-${GIT_SHA}



If failed, see https://builds.apache.org/job/hbase_generate_website/56/console

1 2 >

1 - 100 of 102 matches

Mail list logo