Re: Github Actions

[Greg Stein <gs...@gmail.com>]

It has been a couple months. Have GitHub Actions worked out for you? Can
you share? Are there things needed from Infra?

I would like to know if there is a path for projects to move *off* Jenkins,
Travis, Circle, etc .. and *onto* GitHub Actions. Can GHA solve projects'
needs for CD/CI??

thx,
-g


On Sun, Aug 11, 2019 at 5:31 PM Greg Stein <gs...@gmail.com> wrote:

> On Sun, Aug 11, 2019 at 5:15 PM Francis Chuang <fr...@apache.org>
> wrote:
> >...
>
>> I think there are quite a few ASF projects using gitbox and Github and
>> this would be a very good complement or replacement for Travis, appvoyer
>> and other CI/CD platforms currently in use.
>>
>> Is there any interest from the ASF to enable this for all Gitbox
>> projects when it becomes fully public?
>>
>
> Absolutely. The Infrastructure team would love to see groups try this out,
> and share the experiences here.
>
> If there are any hurdles, then share them and we'll try to knock them down.
>
> I am also interested in being able to push to our website automatically
>> using Github Actions. If the git token that can push to a particular
>> website repository is added as a secret [2] to Github Actions, this
>> would be pretty easy to use for projects to automate the building of
>> their websites.
>>
>
> Should be possible. Again, comes back to groups trying this and reporting
> back how well it went.
>
> Cheers,
> Greg Stein
> Infrastructure Administrator, ASF
>
>

Re: Github Actions

[Francis Chuang <fr...@apache.org>]

For the most part, I've found Github actions to work really well. I've 
migrated Calcite's Avatica Go Driver [1] from Travis to Github Actions. 
I haven't had time to look into the Calcite and Calcite Avatica 
repositories, but I think it should be doable.

The blocker for us is using Actions to automate the publishing of our 
website as mentioned previously. Has infra worked out a way/process to 
enable this? For us, it would simply be a token to push to the 
calcite-site repository in Gitbox (I'd imagine the same token being used 
on the git-website node would suffice) being added as a Github Actions 
secret for us to enable this.

The automation [2] to do this using Github Actions has been tested and 
validated, but we are just missing the credentials to push to the 
calcite-site repo.

Francis

[1] https://github.com/apache/calcite-avatica-go
[2] https://github.com/apache/calcite/tree/test-site/.github/workflows

On 17/10/2019 7:28 pm, Greg Stein wrote:
> It has been a couple months. Have GitHub Actions worked out for you? Can
> you share? Are there things needed from Infra?
> 
> I would like to know if there is a path for projects to move *off* Jenkins,
> Travis, Circle, etc .. and *onto* GitHub Actions. Can GHA solve projects'
> needs for CD/CI??
> 
> thx,
> -g
> 
> 
> On Sun, Aug 11, 2019 at 5:31 PM Greg Stein <gs...@gmail.com> wrote:
> 
>> On Sun, Aug 11, 2019 at 5:15 PM Francis Chuang <fr...@apache.org>
>> wrote:
>>> ...
>>
>>> I think there are quite a few ASF projects using gitbox and Github and
>>> this would be a very good complement or replacement for Travis, appvoyer
>>> and other CI/CD platforms currently in use.
>>>
>>> Is there any interest from the ASF to enable this for all Gitbox
>>> projects when it becomes fully public?
>>>
>>
>> Absolutely. The Infrastructure team would love to see groups try this out,
>> and share the experiences here.
>>
>> If there are any hurdles, then share them and we'll try to knock them down.
>>
>> I am also interested in being able to push to our website automatically
>>> using Github Actions. If the git token that can push to a particular
>>> website repository is added as a secret [2] to Github Actions, this
>>> would be pretty easy to use for projects to automate the building of
>>> their websites.
>>>
>>
>> Should be possible. Again, comes back to groups trying this and reporting
>> back how well it went.
>>
>> Cheers,
>> Greg Stein
>> Infrastructure Administrator, ASF
>>
>>
>