infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francis Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17847) Service accounts for pushing to project Gitbox repositories
Date Thu, 14 Feb 2019 02:52:00 GMT

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

Francis Chuang commented on INFRA-17847:
----------------------------------------

Thanks, Chris! I will subscribe to the list.

> Service accounts for pushing to project Gitbox repositories
> -----------------------------------------------------------
>
>                 Key: INFRA-17847
>                 URL: https://issues.apache.org/jira/browse/INFRA-17847
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: GitBox
>            Reporter: Francis Chuang
>            Priority: Major
>
> My apologies if this is not the correct place to post this as this is more of a question,
but the mailing list is restricted to member of the infra team.
> We are currently in the process of moving our website's repository (https://svn.apache.org/repos/asf/calcite/site)
to Gitbox.
> Our site is generated using a Jekyll, which is then manually committed into the site
repository.
> Does the ASF provide any service accounts for pushing to the site repository? Our use-case
would be to automatically build the site and commit it to the site repository when our contributors
edit certain markdown files in our source repositories (calcite, calcite-avatica and calcite-avatica-go).
Potentially, this would be done via [Github Actions](https://github.com/features/actions)
where the service account is stored as a secret on Github, or via a Jenkins build (where the
service account is stored as a secret on Jenkins).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message