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: Thu, 27 Oct 2016 11:10:40 -0400
Subject: Re: Failure: HBase Generate Website
Message-Id: <D04575D6-4D84-4F33-B3FB-1642F42F66CF@gmail.com>
References: <1941576366.1982.1477579444753.JavaMail.jenkins@crius> <CAKYcnAssqSpRvN0MCR6enSKx8hiVnLPtXd8Ysz=L1o9ygDbU=A@mail.gmail.com>
In-Reply-To: <CAKYcnAssqSpRvN0MCR6enSKx8hiVnLPtXd8Ysz=L1o9ygDbU=A@mail.gmail.com>
To: dev@hbase.apache.org
archived-at: Thu, 27 Oct 2016 15:11:05 -0000

I checked the last QA report on this issue and, while the findbugs and unit t=
est results were red, there was nothing that would indicate the site build w=
ould fail.=20

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?=20

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

> On Oct 27, 2016, at 10:54 AM, Dima Spivak <dimaspivak@apache.org> wrote:
>=20
> HBASE-16886 breaks compilation. Ted, please revert.
>=20
> On Thursday, October 27, 2016, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>=20
>> Build status: Failure
>>=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 o=
f
>> this email.
>>=20
>> 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 rep=
o
>> 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/390/
>> artifact/website.patch.zip | funzip > ${GIT_SHA}.patch
>>  git fetch
>>  git checkout -b asf-site-${GIT_SHA} origin/asf-site
>>  git am --whitespace=3Dfix $GIT_SHA.patch
>>=20
>> At this point, you can preview the changes by opening index.html or any o=
f
>> the other HTML pages in your local asf-site-${GIT_SHA} branch.
>>=20
>> 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:
>>=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-${GIT_SHA}:asf-site
>>  git checkout asf-site
>>  git branch -D asf-site-${GIT_SHA}
>>=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/390/
>> console
>=20
>=20
>=20
> --=20
> -Dima