Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
From: Andrew Purtell <andrew.purtell@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Sun, 9 Oct 2016 09:21:18 -0700
Subject: Re: Fixed: HBase Generate Website
Message-Id: <F7B1437B-F915-41AA-8323-2D72B114F07E@gmail.com>
References: <1817634612.1228.1475938012630.JavaMail.jenkins@crius> <1548895626.1367.1475999820599.JavaMail.jenkins@crius> <CALte62zHVi1V7zKr8gFrJ8PiAmdx6Y+=qQTi_Bx7b5jCBJm1ew@mail.gmail.com> <E9E1AD62-ABE4-46A1-BB37-06AEC43D339B@gmail.com> <CALte62ywwvXyokmFKnz5sdRG3_OwLfj8COcgaUVvZuS1AVZwdg@mail.gmail.com>
In-Reply-To: <CALte62ywwvXyokmFKnz5sdRG3_OwLfj8COcgaUVvZuS1AVZwdg@mail.gmail.com>
To: dev@hbase.apache.org
archived-at: Sun, 09 Oct 2016 16:21:33 -0000

This is your problem. Take ownership. Fix it or I'll revert it.=20

> On Oct 9, 2016, at 9:05 AM, Ted Yu <yuzhihong@gmail.com> wrote:
>=20
> Isn't the RAT check part of the build which generated the 256K patch ?
> If not, we should add it.
>=20
> Which XML file misses the license header ?
>=20
> Is this related to HBASE-16793 ?
>=20
> On Sun, Oct 9, 2016 at 8:43 AM, Andrew Purtell <andrew.purtell@gmail.com>
> wrote:
>=20
>> I tried to copy latest docs from master into the 1.1.7 RC yesterday but
>> the result then failed a RAT check on an XML file missing a header and so=
me
>> jars in src/main/resources . I have not checked today if the situation is=

>> better. Those jars will be binaries appearing in our source tarballs. We o=
k
>> with that?
>>=20
>>> On Oct 9, 2016, at 8:14 AM, Ted Yu <yuzhihong@gmail.com> wrote:
>>>=20
>>> I pushed the artifacts.
>>>=20
>>> On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
>>> jenkins@builds.apache.org> wrote:
>>>=20
>>>> Build status: Fixed
>>>>=20
>>>> 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.
>>>>=20
>>>> Use the following commands to download the patch and apply it to a clea=
n
>>>> branch based on origin/asf-site. If you prefer to keep the hbase-site
>> repo
>>>> around permanently, you can skip the clone step.
>>>>=20
>>>> git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>>>>=20
>>>> cd hbase-site
>>>> wget -O- https://builds.apache.org/job/hbase_generate_website/371/
>>>> artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec
>>>> 52c1c7cb31.patch
>>>> git fetch
>>>> git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
>>>> origin/asf-site
>>>> git am --whitespace=3Dfix e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.patc=
h
>>>>=20
>>>> At this point, you can preview the changes by opening index.html or any=

>> of
>>>> the other HTML pages in your local asf-site-e06c3676f1273f033e3e1
>> 85ee9c1ec52c1c7cb31
>>>> branch.
>>>>=20
>>>> There are lots of spurious changes, such as timestamps and CSS styles i=
n
>>>> tables, so a generic git diff is not very useful. To see a list of file=
s
>>>> that have been added, deleted, renamed, changed type, or are otherwise
>>>> interesting, use the following command:
>>>>=20
>>>> git diff --name-status --diff-filter=3DADCRTXUB origin/asf-site
>>>>=20
>>>> To see only files that had 100 or more lines changed:
>>>>=20
>>>> git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>>>>=20
>>>> When you are satisfied, publish your changes to origin/asf-site using
>>>> these commands:
>>>>=20
>>>> git commit --allow-empty -m "Empty commit" # to work around a current
>>>> ASF INFRA bug
>>>> git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
>>>> 52c1c7cb31:asf-site
>>>> git checkout asf-site
>>>> git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
>>>>=20
>>>> 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.
>>>>=20
>>>> As a courtesy- reply-all to this email to let other committers know you=

>>>> pushed the site.
>>>>=20
>>>>=20
>>>>=20
>>>> If failed, see https://builds.apache.org/job/
>> hbase_generate_website/371/
>>>> console
>>=20