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

Posted to issues@arrow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/09 23:27:00 UTC

[jira] [Updated] (ARROW-6497) [Website] On change to master branch, automatically make PR to asf-site

     [ https://issues.apache.org/jira/browse/ARROW-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ARROW-6497:
----------------------------------
    Labels: pull-request-available  (was: )

> [Website] On change to master branch, automatically make PR to asf-site
> -----------------------------------------------------------------------
>
>                 Key: ARROW-6497
>                 URL: https://issues.apache.org/jira/browse/ARROW-6497
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Website
>            Reporter: Neal Richardson
>            Assignee: Neal Richardson
>            Priority: Major
>              Labels: pull-request-available
>
> I added a build/deploy script to arrow-site that would enable automatically publishing to asf-site when there is a commit to the master branch. However, ASF won't let us add a deploy key to enable this publishing (INFRA-18924). 
> I have a workaround that's not automatic but as close as we can get. On commits to apache/arrow-site's master branch, Travis builds the site and pushes it to a fork of arrow-site (where there is no restriction on deploy keys), and then it makes a PR from there back to the asf-site branch of apache/arrow-site using [hub|https://hub.github.com/hub-pull-request.1.html]. So it's "semiautomatic": the asf-site PR is made automatically, but a committer will need to merge it. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)