infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-18875) Add Github or Gitbox token to Github Actions secrets for automated website deployment
Date Wed, 14 Aug 2019 07:55:00 GMT

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

Daniel Gruno closed INFRA-18875.
--------------------------------
    Resolution: Fixed
      Assignee: Daniel Gruno

Closing this as a duplicate issue. We'll work on the first ticket, and when we have a proper
solution, we'll advise projects.

> Add Github or Gitbox token to Github Actions secrets for automated website deployment
> -------------------------------------------------------------------------------------
>
>                 Key: INFRA-18875
>                 URL: https://issues.apache.org/jira/browse/INFRA-18875
>             Project: Infrastructure
>          Issue Type: Task
>          Components: GitBox, Github
>            Reporter: Francis Chuang
>            Assignee: Daniel Gruno
>            Priority: Major
>
> As noted on the builds@ list, I've started experimenting with Github Actions to automate
the deployment of the Calcite website: https://lists.apache.org/thread.html/246c44267ddaede1cda516c4c825a3868cf617dbe09a6106a8a29d92@%3Cbuilds.apache.org%3E
> I have now gotten the build to work correctly (see https://github.com/apache/calcite/runs/192859421)
and the remaining step is to gain credentials to push the changes to our site repository.
> We would like to have changes to our source repos in the following to push to the website
repo (https://github.com/apache/calcite-site):
> - https://github.com/apache/calcite
> - https://github.com/apache/calcite-avatica
> - https://github.com/apache/calcite-avatica-go
> For the credentials, it's possible to store them as a Github Actions secret by following
these instructions: https://help.github.com/en/articles/virtual-environments-for-github-actions#creating-and-using-secrets-encrypted-variables
> I think the following types of tokens would allow us to achieve this:
> - A Gitbox token to push to gitbox (like the one currently used by the Jenkins git-websites
node).
> - A Github token with write access to repositories in the Apache organization on Github.
> This is probably the first use of Github Actions to publish to another repository, so
I am very amendable to working with INFRA for a suitable solution.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message