patch is up on:
https://issues.apache.org/jira/browse/HBASE-17192
On Tue, Nov 29, 2016 at 3:37 AM, Sean Busbey <bus...@apache.org> wrote:
> I have figured out the problem. jira in a few.
>
> On Tue, Nov 29, 2016 at 3:23 AM, Sean Busbey <bus...@apache.org> wrote:
>> git bisect led me to the commit immediately after our last known good
>> job. Reverting that commit didn't fix things. Attempting a new build
>> from the same commit used in our last known good job also failed with
>> the current error.
>>
>> I'm checking on some other leads and will follow up tomorrow.
>>
>> On Mon, Nov 28, 2016 at 4:03 PM, Sean Busbey <bus...@cloudera.com> wrote:
>>> no idea. it's not often I see new cryptic maven errors. :/
>>>
>>> anyone have time to do a git bisect? about a week of changes shouldn't
>>> take too long.
>>>
>>> On Mon, Nov 28, 2016 at 10:01 AM, Dima Spivak <dimaspi...@apache.org> wrote:
>>>> 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 <
>>>> jenk...@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
>>>
>>>
>>>
>>> --
>>> busbey
