You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2022/04/29 22:59:00 UTC

[jira] [Commented] (THRIFT-5564) Migrate to GitHub Actions and replace Travis and Appveyor

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

Jens Geyer commented on THRIFT-5564:
------------------------------------

> Using GitHub Actions will solve both issues since it is 
There is a "hopefully" missing.  I don't believe it until I see it. Every new system always promises "this is the last system you will ever need". And then comes the next one.

That being said, appreciate the work you guys do on this!

 

> Migrate to GitHub Actions and replace Travis and Appveyor
> ---------------------------------------------------------
>
>                 Key: THRIFT-5564
>                 URL: https://issues.apache.org/jira/browse/THRIFT-5564
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Build Process, Deployment
>            Reporter: Liu Jiayu
>            Assignee: Liu Jiayu
>            Priority: Major
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> Recently Travis CI has been unstable, failing with arcane error messages, queued up for extended amount of time, or sometimes just totally missing build logs. It's also not convenient to have another build system Appveyor.
> Using GitHub Actions will solve both issues since it is more stable, more user friendly, and can handle most of Linux, Windows, and macOS (excluding M1) arch.
> The migration process can be in parallel, i.e. have GitHub Actions fully setup before moving off the original CI systems.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)