Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
References: <5838826.3129.1480257267649.JavaMail.jenkins@crius> <62091829.3311.1480343670783.JavaMail.jenkins@crius>
In-Reply-To: <62091829.3311.1480343670783.JavaMail.jenkins@crius>
From: Dima Spivak <dimaspivak@apache.org>
Date: Mon, 28 Nov 2016 16:01:09 +0000
Message-ID: <CAKYcnAv=GAh=tku7r6NKQ-eaCVP4BfPAaVLFCXwaFk+0Dvwh3g@mail.gmail.com>
Subject: Re: Still Failing: HBase Generate Website
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b471d641d6c0705425e95fb
archived-at: Mon, 28 Nov 2016 16:01:23 -0000

--047d7b471d641d6c0705425e95fb
Content-Type: text/plain; charset=UTF-8

Anyone know what's up here? I don't see any obvious breaking changes, but
mvn site fails in parent module with:

--------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
project hbase: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.4:site failed: For artifact
{null:null:null:jar}: The groupId cannot be empty. -> [Help 1]
[ERROR]

On Mon, Nov 28, 2016 at 6:34 AM Apache Jenkins Server <
jenkins@builds.apache.org> wrote:

> Build status: Still Failing
>
> 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/419/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/419/console

--047d7b471d641d6c0705425e95fb--