Re: Successful: HBase Generate Website

[Josh Elser]

+1 to that :D

Stack wrote:

Hot Dog!

On Fri, Mar 31, 2017 at 3:03 PM, Misty Stanley-Jones
wrote:


FYI, the linked Jenkins job now automatically updates the site! No more
need to manually push. Merry Christmas! :)

- Original message -
From: Apache Jenkins Server
To: dev@hbase.apache.org
Subject: Successful: HBase Generate Website
Date: Fri, 31 Mar 2017 21:32:17 + (UTC)

Build status: Successful

If successful, the website and docs have been generated and the site has
been updated automatically.
If failed, see
https://builds.apache.org/job/hbase_generate_website/561/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/561/
artifact/website.patch.zip
   | funzip>  1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7.patch
   git fetch
   git checkout -b asf-site-1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7
   origin/asf-site
   git am --whitespace=fix 1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7.patch
   git push origin
   asf-site-1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7: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-1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7

Re: Successful: HBase Generate Website

[Stack]

Hot Dog!

On Fri, Mar 31, 2017 at 3:03 PM, Misty Stanley-Jones 
wrote:

> FYI, the linked Jenkins job now automatically updates the site! No more
> need to manually push. Merry Christmas! :)
>
> - Original message -
> From: Apache Jenkins Server 
> To: dev@hbase.apache.org
> Subject: Successful: HBase Generate Website
> Date: Fri, 31 Mar 2017 21:32:17 + (UTC)
>
> Build status: Successful
>
> If successful, the website and docs have been generated and the site has
> been updated automatically.
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/561/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/561/
> artifact/website.patch.zip
>   | funzip > 1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7.patch
>   git fetch
>   git checkout -b asf-site-1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7
>   origin/asf-site
>   git am --whitespace=fix 1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7.patch
>   git push origin
>   asf-site-1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7: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-1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7
>
>
>
>

Re: Successful: HBase Generate Website

[Sean Busbey]

I published this version.

On Wed, Mar 29, 2017 at 3:51 PM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/552/artifact/website.patch.zip
>  | funzip > b290d14e1f7fffa3c06bb19770b53094c3d2459a.patch
>   git fetch
>   git checkout -b asf-site-b290d14e1f7fffa3c06bb19770b53094c3d2459a 
> origin/asf-site
>   git am --whitespace=fix b290d14e1f7fffa3c06bb19770b53094c3d2459a.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-b290d14e1f7fffa3c06bb19770b53094c3d2459a 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-b290d14e1f7fffa3c06bb19770b53094c3d2459a:asf-site
>   git checkout asf-site
>   git branch -D asf-site-b290d14e1f7fffa3c06bb19770b53094c3d2459a
>
> 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/552/console

Re: Successful: HBase Generate Website

[Stack]

I pushed the website with below patch.
FYI,
S

On Fri, Feb 17, 2017 at 7:02 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/491/
> artifact/website.patch.zip | funzip > 7763dd6688254d37ad611f5d290db4
> 7c83cf93d3.patch
>   git fetch
>   git checkout -b asf-site-7763dd6688254d37ad611f5d290db47c83cf93d3
> origin/asf-site
>   git am --whitespace=fix 7763dd6688254d37ad611f5d290db47c83cf93d3.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-7763dd6688254d37ad611f5d290db47c83cf93d3
> 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-7763dd6688254d37ad611f5d290db4
> 7c83cf93d3:asf-site
>   git checkout asf-site
>   git branch -D asf-site-7763dd6688254d37ad611f5d290db47c83cf93d3
>
> 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/491/
> console

Re: Successful: HBase Generate Website

[Ted Yu]

Looks like the site hasn't been updated for almost 2 months.

I have pushed the 26a94844f533b95db1f0a58d6a7cc3dc4a7a7098.patch

On Sun, Feb 5, 2017 at 7:07 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/480/
> artifact/website.patch.zip | funzip > 26a94844f533b95db1f0a58d6a7cc3
> dc4a7a7098.patch
>   git fetch
>   git checkout -b asf-site-26a94844f533b95db1f0a58d6a7cc3dc4a7a7098
> origin/asf-site
>   git am --whitespace=fix 26a94844f533b95db1f0a58d6a7cc3dc4a7a7098.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-26a94844f533b95db1f0a58d6a7cc3dc4a7a7098
> 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-26a94844f533b95db1f0a58d6a7cc3
> dc4a7a7098:asf-site
>   git checkout asf-site
>   git branch -D asf-site-26a94844f533b95db1f0a58d6a7cc3dc4a7a7098
>
> 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/480/
> console

Re: Successful: HBase Generate Website

[Stack]

FYI, I pushed this patch just now.
St.Ack

On Wed, Dec 7, 2016 at 6:57 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/429/
> artifact/website.patch.zip | funzip > 61220e4d7c8d7e5fb8ed3bbe2469bc
> 86632c48de.patch
>   git fetch
>   git checkout -b asf-site-61220e4d7c8d7e5fb8ed3bbe2469bc86632c48de
> origin/asf-site
>   git am --whitespace=fix 61220e4d7c8d7e5fb8ed3bbe2469bc86632c48de.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-61220e4d7c8d7e5fb8ed3bbe2469bc86632c48de
> 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-61220e4d7c8d7e5fb8ed3bbe2469bc
> 86632c48de:asf-site
>   git checkout asf-site
>   git branch -D asf-site-61220e4d7c8d7e5fb8ed3bbe2469bc86632c48de
>
> 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/429/
> console

Re: Successful: HBase Generate Website

[Stack]

I pushed this change.
St.Ack

On Tue, Nov 15, 2016 at 6:58 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/406/
> artifact/website.patch.zip | funzip > 4d1bff9e78884adf689dd587d65afe
> 36a336c56b.patch
>   git fetch
>   git checkout -b asf-site-4d1bff9e78884adf689dd587d65afe36a336c56b
> origin/asf-site
>   git am --whitespace=fix 4d1bff9e78884adf689dd587d65afe36a336c56b.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-4d1bff9e78884adf689dd587d65afe36a336c56b
> 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-4d1bff9e78884adf689dd587d65afe
> 36a336c56b:asf-site
>   git checkout asf-site
>   git branch -D asf-site-4d1bff9e78884adf689dd587d65afe36a336c56b
>
> 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/406/
> console

Re: Successful: HBase Generate Website

[Stack]

Looks like INFRA has been messing w/ labels (looking over on builds@)... An
edit of the machine list got me going again.
St.Ack

On Thu, Nov 10, 2016 at 4:25 PM, Stack  wrote:

> This job has stopped running blocked waiting on machine type:
>
> #4​01
> 
> (pending—There are no nodes with the label ‘(ubuntu&)&&!jenkins-
> cloud-4GB&&!H11
> 
> ’)
>
> https://builds.apache.org/job/hbase_generate_website/
>
> Asking here before I go to infra to see if these labels have been removed.
>
> Thanks,
> St.Ack
>
> On Mon, Nov 7, 2016 at 7:09 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
>> Build status: Successful
>>
>> 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/400/art
>> ifact/website.patch.zip | funzip > 28de528c6ea19c261213ee229381a1
>> 8ed3b5ef94.patch
>>   git fetch
>>   git checkout -b asf-site-28de528c6ea19c261213ee229381a18ed3b5ef94
>> origin/asf-site
>>   git am --whitespace=fix 28de528c6ea19c261213ee229381a18ed3b5ef94.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-28de528c6ea19c261213ee229381a18ed3b5ef94
>> 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-28de528c6ea19c261213e
>> e229381a18ed3b5ef94:asf-site
>>   git checkout asf-site
>>   git branch -D asf-site-28de528c6ea19c261213ee229381a18ed3b5ef94
>>
>> 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/400/console
>
>
>

Re: Successful: HBase Generate Website

[Stack]

This job has stopped running blocked waiting on machine type:

#4​01

(pending—There are no nodes with the label ‘
(ubuntu&)&&!jenkins-cloud-4GB&&!H11

’)

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

Asking here before I go to infra to see if these labels have been removed.

Thanks,
St.Ack

On Mon, Nov 7, 2016 at 7:09 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/400/
> artifact/website.patch.zip | funzip > 28de528c6ea19c261213ee229381a1
> 8ed3b5ef94.patch
>   git fetch
>   git checkout -b asf-site-28de528c6ea19c261213ee229381a18ed3b5ef94
> origin/asf-site
>   git am --whitespace=fix 28de528c6ea19c261213ee229381a18ed3b5ef94.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-28de528c6ea19c261213ee229381a18ed3b5ef94
> 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-28de528c6ea19c261213ee229381a1
> 8ed3b5ef94:asf-site
>   git checkout asf-site
>   git branch -D asf-site-28de528c6ea19c261213ee229381a18ed3b5ef94
>
> 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/400/
> console

Re: Successful: HBase Generate Website

[Dima Spivak]

Pushed.

-Dima

On Mon, Oct 17, 2016 at 7:57 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/381/art
> ifact/website.patch.zip | funzip > 278625312047a2100f4dbb2d2eaa4e
> 2219d00e14.patch
>   git fetch
>   git checkout -b asf-site-278625312047a2100f4dbb2d2eaa4e2219d00e14
> origin/asf-site
>   git am --whitespace=fix 278625312047a2100f4dbb2d2eaa4e2219d00e14.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-278625312047a2100f4dbb2d2eaa4e2219d00e14
> 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-278625312047a2100f4db
> b2d2eaa4e2219d00e14:asf-site
>   git checkout asf-site
>   git branch -D asf-site-278625312047a2100f4dbb2d2eaa4e2219d00e14
>
> 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/381/console

Re: Successful: HBase Generate Website

[Dima Spivak]

Pushed.

-Dima

On Thu, Sep 29, 2016 at 11:25 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/359/
> artifact/website.patch.zip | funzip > 63808a224c8689d07e55f90efd25f9
> 597b0d04dd.patch
>   git fetch
>   git checkout -b asf-site-63808a224c8689d07e55f90efd25f9597b0d04dd
> origin/asf-site
>   git am --whitespace=fix 63808a224c8689d07e55f90efd25f9597b0d04dd.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-63808a224c8689d07e55f90efd25f9597b0d04dd
> 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-63808a224c8689d07e55f90efd25f9
> 597b0d04dd:asf-site
>   git checkout asf-site
>   git branch -D asf-site-63808a224c8689d07e55f90efd25f9597b0d04dd
>
> 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/359/
> console

Re: Successful: HBase Generate Website

[Misty Stanley-Jones]

Pushed.

On Sat, Sep 17, 2016, at 12:59 AM, Apache Jenkins Server wrote:
> Build status: Successful
> 
> 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/346/artifact/website.patch.zip
>   | funzip > 2597217ae5aa057e1931c772139ce8cc7a2b3efb.patch
>   git fetch
>   git checkout -b asf-site-2597217ae5aa057e1931c772139ce8cc7a2b3efb
>   origin/asf-site
>   git am --whitespace=fix 2597217ae5aa057e1931c772139ce8cc7a2b3efb.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-2597217ae5aa057e1931c772139ce8cc7a2b3efb 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-2597217ae5aa057e1931c772139ce8cc7a2b3efb:asf-site
>   git checkout asf-site
>   git branch -D asf-site-2597217ae5aa057e1931c772139ce8cc7a2b3efb
> 
> 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/346/console

Re: Successful: HBase Generate Website

[Dima Spivak]

Pushed.

-Dima

On Thu, Sep 15, 2016 at 7:51 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/345/
> artifact/website.patch.zip | funzip > 56be3ac7c8d203710f844cd799f2fa
> 3496f0515a.patch
>   git fetch
>   git checkout -b asf-site-56be3ac7c8d203710f844cd799f2fa3496f0515a
> origin/asf-site
>   git am --whitespace=fix 56be3ac7c8d203710f844cd799f2fa3496f0515a.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-56be3ac7c8d203710f844cd799f2fa3496f0515a
> 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-56be3ac7c8d203710f844cd799f2fa
> 3496f0515a:asf-site
>   git checkout asf-site
>   git branch -D asf-site-56be3ac7c8d203710f844cd799f2fa3496f0515a
>
> 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/345/
> console

Re: Successful: HBase Generate Website

[Misty Stanley-Jones]

Pushed.

On Wed, Sep 7, 2016, at 12:55 AM, Apache Jenkins Server wrote:
> Build status: Successful
> 
> 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/334/artifact/website.patch.zip
>   | funzip > b6ba13c37715422710a142f6f82ba4817129c3d6.patch
>   git fetch
>   git checkout -b asf-site-b6ba13c37715422710a142f6f82ba4817129c3d6
>   origin/asf-site
>   git am --whitespace=fix b6ba13c37715422710a142f6f82ba4817129c3d6.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-b6ba13c37715422710a142f6f82ba4817129c3d6 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-b6ba13c37715422710a142f6f82ba4817129c3d6:asf-site
>   git checkout asf-site
>   git branch -D asf-site-b6ba13c37715422710a142f6f82ba4817129c3d6
> 
> 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/334/console

Re: Successful: HBase Generate Website

[Dima Spivak]

Pushed.

-Dima

On Mon, Sep 5, 2016 at 7:57 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/333/
> artifact/website.patch.zip | funzip > b6ba13c37715422710a142f6f82ba4
> 817129c3d6.patch
>   git fetch
>   git checkout -b asf-site-b6ba13c37715422710a142f6f82ba4817129c3d6
> origin/asf-site
>   git am --whitespace=fix b6ba13c37715422710a142f6f82ba4817129c3d6.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-b6ba13c37715422710a142f6f82ba4817129c3d6
> 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-b6ba13c37715422710a142f6f82ba4
> 817129c3d6:asf-site
>   git checkout asf-site
>   git branch -D asf-site-b6ba13c37715422710a142f6f82ba4817129c3d6
>
> 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/333/
> console

Re: Successful: HBase Generate Website

[Dima Spivak]

Pushed.

-Dima

On Sun, Sep 4, 2016 at 7:55 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/332/
> artifact/website.patch.zip | funzip > ab07f0087b8c5efcb1b084e42f4941
> ddb0c8885e.patch
>   git fetch
>   git checkout -b asf-site-ab07f0087b8c5efcb1b084e42f4941ddb0c8885e
> origin/asf-site
>   git am --whitespace=fix ab07f0087b8c5efcb1b084e42f4941ddb0c8885e.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-ab07f0087b8c5efcb1b084e42f4941ddb0c8885e
> 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-ab07f0087b8c5efcb1b084e42f4941
> ddb0c8885e:asf-site
>   git checkout asf-site
>   git branch -D asf-site-ab07f0087b8c5efcb1b084e42f4941ddb0c8885e
>
> 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/332/
> console

Re: Successful: HBase Generate Website

[Dima Spivak]

Pushed.

-Dima

On Fri, Sep 2, 2016 at 7:58 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/330/
> artifact/website.patch.zip | funzip > f6ccae350203ec35f3b7acd75431a5
> abd7e9f5a8.patch
>   git fetch
>   git checkout -b asf-site-f6ccae350203ec35f3b7acd75431a5abd7e9f5a8
> origin/asf-site
>   git am --whitespace=fix f6ccae350203ec35f3b7acd75431a5abd7e9f5a8.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-f6ccae350203ec35f3b7acd75431a5abd7e9f5a8
> 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-f6ccae350203ec35f3b7acd75431a5
> abd7e9f5a8:asf-site
>   git checkout asf-site
>   git branch -D asf-site-f6ccae350203ec35f3b7acd75431a5abd7e9f5a8
>
> 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/330/
> console

Re: Successful: HBase Generate Website

[Dima Spivak]

Pushed.

-Dima

On Thu, Sep 1, 2016 at 8:09 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/329/art
> ifact/website.patch.zip | funzip > e30a66b9443618f04ad8cb0aee96ac
> 77b174338b.patch
>   git fetch
>   git checkout -b asf-site-e30a66b9443618f04ad8cb0aee96ac77b174338b
> origin/asf-site
>   git am --whitespace=fix e30a66b9443618f04ad8cb0aee96ac77b174338b.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-e30a66b9443618f04ad8cb0aee96ac77b174338b
> 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-e30a66b9443618f04ad8c
> b0aee96ac77b174338b:asf-site
>   git checkout asf-site
>   git branch -D asf-site-e30a66b9443618f04ad8cb0aee96ac77b174338b
>
> 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/329/console

Re: Successful: HBase Generate Website

[Sean Busbey]

pushed.

On Sun, Aug 7, 2016 at 9:54 AM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/309/artifact/website.patch.zip
>  | funzip > 30d7eeaefe431bc263519064662e6dc8ad8ff05a.patch
>   git fetch
>   git checkout -b asf-site-30d7eeaefe431bc263519064662e6dc8ad8ff05a 
> origin/asf-site
>   git am --whitespace=fix 30d7eeaefe431bc263519064662e6dc8ad8ff05a.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-30d7eeaefe431bc263519064662e6dc8ad8ff05a 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-30d7eeaefe431bc263519064662e6dc8ad8ff05a:asf-site
>   git checkout asf-site
>   git branch -D asf-site-30d7eeaefe431bc263519064662e6dc8ad8ff05a
>
> 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/309/console



-- 
Sean

Re: Successful: HBase Generate Website

[Sean Busbey]

pushed live.

On Mon, Aug 1, 2016 at 10:00 AM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/303/artifact/website.patch.zip
>  | funzip > 2c5a0fcf1f216ac5333a2047f6ce69797a5da14b.patch
>   git fetch
>   git checkout -b asf-site-2c5a0fcf1f216ac5333a2047f6ce69797a5da14b 
> origin/asf-site
>   git am --whitespace=fix 2c5a0fcf1f216ac5333a2047f6ce69797a5da14b.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-2c5a0fcf1f216ac5333a2047f6ce69797a5da14b 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-2c5a0fcf1f216ac5333a2047f6ce69797a5da14b:asf-site
>   git checkout asf-site
>   git branch -D asf-site-2c5a0fcf1f216ac5333a2047f6ce69797a5da14b
>
> 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/303/console



-- 
busbey

Re: Successful: HBase Generate Website

[Misty Stanley-Jones]

Pushed.

On Tue, Jul 26, 2016 at 8:28 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> 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/298/artifact/website.patch.zip
> | funzip > bcf409e11f081be077f1232c987d05fa78a1793c.patch
>   git fetch
>   git checkout -b asf-site-bcf409e11f081be077f1232c987d05fa78a1793c
> origin/asf-site
>   git am --whitespace=fix bcf409e11f081be077f1232c987d05fa78a1793c.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-bcf409e11f081be077f1232c987d05fa78a1793c 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-bcf409e11f081be077f1232c987d05fa78a1793c:asf-site
>   git checkout asf-site
>   git branch -d asf-site-bcf409e11f081be077f1232c987d05fa78a1793c
>
> 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.
>
>
>
>
>
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/298/console

Re: Successful: HBase Generate Website

[Sean Busbey]

pushed.

On Sun, Jul 24, 2016 at 10:09 AM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/297/artifact/website.patch.zip
>  | funzip > bdd7782f054a4740bb63f4d9781ffe083d51e4bf.patch
>   git fetch
>   git checkout -b asf-site-bdd7782f054a4740bb63f4d9781ffe083d51e4bf 
> origin/asf-site
>   git am --whitespace=fix bdd7782f054a4740bb63f4d9781ffe083d51e4bf.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-bdd7782f054a4740bb63f4d9781ffe083d51e4bf 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-bdd7782f054a4740bb63f4d9781ffe083d51e4bf:asf-site
>   git checkout asf-site
>   git branch -d asf-site-bdd7782f054a4740bb63f4d9781ffe083d51e4bf
>
> 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.
>
>
>
>
>
> If failed, see 
> https://builds.apache.org/job/hbase_generate_website/297/console



-- 
busbey

Re: Successful: HBase Generate Website

[Sean Busbey]

pushed

On Wed, Jul 20, 2016 at 12:07 PM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/293/artifact/website.patch.zip
>  | funzip > 70f330dc844af88b5bd3de69e271181e40bc58be.patch
>   git fetch
>   git checkout -b asf-site-70f330dc844af88b5bd3de69e271181e40bc58be 
> origin/asf-site
>   git am --whitespace=fix 70f330dc844af88b5bd3de69e271181e40bc58be.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-70f330dc844af88b5bd3de69e271181e40bc58be 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-70f330dc844af88b5bd3de69e271181e40bc58be:asf-site
>   git checkout asf-site
>   git branch -d asf-site-70f330dc844af88b5bd3de69e271181e40bc58be
>
> 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.
>
>
>
>
>
> If failed, see 
> https://builds.apache.org/job/hbase_generate_website/293/console



-- 
busbey

Re: Successful: HBase Generate Website

[Sean Busbey]

pushed.

On Tue, Jul 19, 2016 at 10:04 AM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/292/artifact/website.patch.zip
>  | funzip > 9454daf25bcc704d8403a403282c9bf0090b1101.patch
>   git fetch
>   git checkout -b asf-site-9454daf25bcc704d8403a403282c9bf0090b1101 
> origin/asf-site
>   git am --whitespace=fix 9454daf25bcc704d8403a403282c9bf0090b1101.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-9454daf25bcc704d8403a403282c9bf0090b1101 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-9454daf25bcc704d8403a403282c9bf0090b1101:asf-site
>   git checkout asf-site
>   git branch -d asf-site-9454daf25bcc704d8403a403282c9bf0090b1101
>
> 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.
>
>
>
>
>
> If failed, see 
> https://builds.apache.org/job/hbase_generate_website/292/console



-- 
busbey

Re: Successful: HBase Generate Website

[Sean Busbey]

pushed.

On Sun, Jul 17, 2016 at 9:55 AM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/290/artifact/website.patch.zip
>  | funzip > 9bc7ecfb9dec6bfe14a12b6d3bfd11392d7752b8.patch
>   git fetch
>   git checkout -b asf-site-9bc7ecfb9dec6bfe14a12b6d3bfd11392d7752b8 
> origin/asf-site
>   git am --whitespace=fix 9bc7ecfb9dec6bfe14a12b6d3bfd11392d7752b8.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-9bc7ecfb9dec6bfe14a12b6d3bfd11392d7752b8 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-9bc7ecfb9dec6bfe14a12b6d3bfd11392d7752b8:asf-site
>   git checkout asf-site
>   git branch -d asf-site-9bc7ecfb9dec6bfe14a12b6d3bfd11392d7752b8
>
> 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.
>
>
>
>
>
> If failed, see 
> https://builds.apache.org/job/hbase_generate_website/290/console

Re: Successful: HBase Generate Website

[Sean Busbey]

pushed.

On Thu, Jul 14, 2016 at 10:01 AM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/287/artifact/website.patch.zip
>  | funzip > a55af38689fbe273e716ebbf6191e9515986dbf3.patch
>   git fetch
>   git checkout -b asf-site-a55af38689fbe273e716ebbf6191e9515986dbf3 
> origin/asf-site
>   git am --whitespace=fix a55af38689fbe273e716ebbf6191e9515986dbf3.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-a55af38689fbe273e716ebbf6191e9515986dbf3 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-a55af38689fbe273e716ebbf6191e9515986dbf3:asf-site
>   git checkout asf-site
>   git branch -d asf-site-a55af38689fbe273e716ebbf6191e9515986dbf3
>
> 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.
>
>
>
>
>
> If failed, see 
> https://builds.apache.org/job/hbase_generate_website/287/console

Re: Successful: HBase Generate Website

[Misty Stanley-Jones]

<3

On Tue, Jul 12, 2016 at 8:41 AM, Sean Busbey  wrote:

> pushed.
>
> On Tue, Jul 12, 2016 at 9:59 AM, Apache Jenkins Server
>  wrote:
> > Build status: Successful
> >
> > 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/285/artifact/website.patch.zip
> | funzip > 2650711e944244b3b87e6d6805b7716b216e8786.patch
> >   git fetch
> >   git checkout -b asf-site-2650711e944244b3b87e6d6805b7716b216e8786
> origin/asf-site
> >   git am --whitespace=fix 2650711e944244b3b87e6d6805b7716b216e8786.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-2650711e944244b3b87e6d6805b7716b216e8786 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-2650711e944244b3b87e6d6805b7716b216e8786:asf-site
> >   git checkout asf-site
> >   git branch -d asf-site-2650711e944244b3b87e6d6805b7716b216e8786
> >
> > 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.
> >
> >
> >
> >
> >
> > If failed, see
> https://builds.apache.org/job/hbase_generate_website/285/console
>

Re: Successful: HBase Generate Website

[Sean Busbey]

pushed.

On Tue, Jul 12, 2016 at 9:59 AM, Apache Jenkins Server
 wrote:
> Build status: Successful
>
> 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/285/artifact/website.patch.zip
>  | funzip > 2650711e944244b3b87e6d6805b7716b216e8786.patch
>   git fetch
>   git checkout -b asf-site-2650711e944244b3b87e6d6805b7716b216e8786 
> origin/asf-site
>   git am --whitespace=fix 2650711e944244b3b87e6d6805b7716b216e8786.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-2650711e944244b3b87e6d6805b7716b216e8786 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-2650711e944244b3b87e6d6805b7716b216e8786:asf-site
>   git checkout asf-site
>   git branch -d asf-site-2650711e944244b3b87e6d6805b7716b216e8786
>
> 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.
>
>
>
>
>
> If failed, see 
> https://builds.apache.org/job/hbase_generate_website/285/console

Re: Successful: HBase Generate Website

[Misty Stanley-Jones]

Refreshed.

On Tue, Nov 24, 2015 at 1:01 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Successful
>
> If successful, the website and docs have been generated. Use the following
> commands to publish the website:
>
> wget -O-
> https://builds.apache.org/job/hbase_generate_website/40/artifact/website.patch.zip
> | bsdtar xf -
> git checkout asf-site && git pull && git am
> 55087ce8887b5be38b0fda0dda3fbf2f92c13778.patch && git push origin asf-site
>
> If failed, see
> https://builds.apache.org/job/hbase_generate_website/40/console

Re: Successful: HBase Generate Website

[Stack]

Excellent.

On Mon, Nov 2, 2015 at 9:52 PM, Misty Stanley-Jones <
mstanleyjo...@cloudera.com> wrote:

> I set up a Jenkins job to do the heavy lifting of building and publishing
> the website. All you need to do is paste the commands from the email from
> Jenkins. You don't even need to worry about keeping the SVN repo up to
> date. Hope this is helpful!
>
> Right now, this will run daily. We can tune it down if it's too often.
>
> -- Forwarded message --
> From: Apache Jenkins Server 
> Date: Tue, Nov 3, 2015 at 3:48 PM
> Subject: Successful: HBase Generate Website
> To: dev@hbase.apache.org
>
>
> Successful
>
> If successful, AND you have SVN commit access, paste the following into a
> command prompt to publish the website:
>
> wget
>
> https://builds.apache.org/job/HBase%20Generate%20Website/9/artifact/trunk.tar.gz
> tar xzvf trunk.tar.gz
> cd trunk
> svn commit -F ./commit_msg.txt
>
> If failed, see
> https://builds.apache.org/job/HBase%20Generate%20Website/9/console
>

Re: Successful: HBase Generate Website

[Enis Söztutar]

This is great. Thanks Misty.

FYI: https://issues.apache.org/jira/browse/HBASE-14751

On Tue, Nov 3, 2015 at 9:02 AM, Stack  wrote:

> Excellent.
>
> On Mon, Nov 2, 2015 at 9:52 PM, Misty Stanley-Jones <
> mstanleyjo...@cloudera.com> wrote:
>
> > I set up a Jenkins job to do the heavy lifting of building and publishing
> > the website. All you need to do is paste the commands from the email from
> > Jenkins. You don't even need to worry about keeping the SVN repo up to
> > date. Hope this is helpful!
> >
> > Right now, this will run daily. We can tune it down if it's too often.
> >
> > -- Forwarded message --
> > From: Apache Jenkins Server 
> > Date: Tue, Nov 3, 2015 at 3:48 PM
> > Subject: Successful: HBase Generate Website
> > To: dev@hbase.apache.org
> >
> >
> > Successful
> >
> > If successful, AND you have SVN commit access, paste the following into a
> > command prompt to publish the website:
> >
> > wget
> >
> >
> https://builds.apache.org/job/HBase%20Generate%20Website/9/artifact/trunk.tar.gz
> > tar xzvf trunk.tar.gz
> > cd trunk
> > svn commit -F ./commit_msg.txt
> >
> > If failed, see
> > https://builds.apache.org/job/HBase%20Generate%20Website/9/console
> >
>