The patch has now been merged and the Jenkins jobs have been converted to
use the scripts from version control. The website-generation script has
successfully run and the link checker script is currently running and looks
like it will be fine. Thanks for the quick turnaround on reviews!

On Wed, Aug 9, 2017 at 2:39 PM, Misty Stanley-Jones <mi...@apache.org>
wrote:

> https://issues.apache.org/jira/browse/HBASE-18548 Patch attached and
> ready for review. Thanks, y'all!
>
> On Wed, Aug 9, 2017 at 1:22 PM, Misty Stanley-Jones <mi...@apache.org>
> wrote:
>
>> I got this.
>>
>> On Wed, Aug 9, 2017 at 12:17 PM, Sean Busbey <bus...@apache.org> wrote:
>>
>>> could someone file a JIRA to get the website update job into source
>>> control? it should be pretty straight forward; even if just the shell
>>> script goes into dev-support it would make this a lot easier to
>>> maintain over time. I'm happy to do the implementation, I'm just
>>> likely to forget about it when I end up with the time.
>>>
>>> On Wed, Aug 9, 2017 at 1:29 PM, Stack <st...@duboce.net> wrote:
>>> > I pushed a fix on HBASE-18545 that should take care of it.
>>> >
>>> > I repro'd the issue by running commands found in the jenkins config.
>>> >
>>> > HBASE-18545 is the issue. Building rsgroups, it couldn't find protos
>>> files
>>> > it depends on that are over in hbase-protocol.
>>> >
>>> > S
>>> >
>>> >
>>> > On Wed, Aug 9, 2017 at 8:25 AM, Mike Drob <md...@apache.org> wrote:
>>> >
>>> >> I tried to look at this failure on Jenkins, but couldn't make sense
>>> of it
>>> >> -- there's barely any information there. Does anybody else have
>>> experience
>>> >> with this job?
>>> >>
>>> >> Mike
>>> >>
>>> >> On Wed, Aug 9, 2017 at 9:53 AM, Apache Jenkins Server <
>>> >> jenk...@builds.apache.org> wrote:
>>> >>
>>> >> > Build status: Still Failing
>>> >> >
>>> >> > The HBase website has not been updated to incorporate HBase commit
>>> >> > ${HBASE_GIT_SHA}.
>>> >> >
>>> >> > See https://builds.apache.org/job/hbase_generate_website/1075/co
>>> nsole
>>> >>
>>>
>>
>>
>

Reply via email to