You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2016/04/14 16:51:25 UTC

[jira] [Commented] (INFRA-10751) Large commits to asf-site do not trigger site rebuild

    [ https://issues.apache.org/jira/browse/INFRA-10751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241304#comment-15241304 ] 

Sean Busbey commented on INFRA-10751:
-------------------------------------

this just happened to Yetus on [commit 3510a128|https://git-wip-us.apache.org/repos/asf?p=yetus.git;a=commit;h=3510a128e53fe0f257f02f041c6637e67a7e0cc2].

I pushed [an empty commit|https://git-wip-us.apache.org/repos/asf?p=yetus.git;a=commit;h=8322f357b1f04b717a35b29ef1b3b318db546e8c] and things picked up again.

> Large commits to asf-site do not trigger site rebuild
> -----------------------------------------------------
>
>                 Key: INFRA-10751
>                 URL: https://issues.apache.org/jira/browse/INFRA-10751
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Website
>            Reporter: Misty Stanley-Jones
>            Assignee: Daniel Takamori
>
> Several times now, I have done large commits to asf-site branch, pushed them, and gitsubpub did not get triggered. I have to do a follow-on trivial commit, and then it is triggered. This is a bit of a problem, because we have some auto-generated content that will always have a few lines different. These add up to a big commit.
> I can tell when it is not going to work when my commit doesn't show up in #asfbot IRC channel.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)