[
https://issues.apache.org/jira/browse/THRIFT-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530293#comment-17530293
]
Liu Jiayu commented on THRIFT-5564:
-----------------------------------
I agree with you - we shall see if the promise can hold. [~jensg]
For now the migration is a bit complex as I'm not familiar with the release
process myself, so I've decided to take a multi-phase approach:
# migrate CI only, no changes to travis
## migrate compiler building
## migrate library building
## migrate crosstest
# migrate CD only, no changes to travis
## tag-push triggered release job, but do no uploads
## verify the artifact are good
## figure out how to store secrets in GitHub workflow (need PMC help)
# then deprecate travis CI part
# try a release with GitHub workflow
# if that's successful, deprecate Travis CD
All the above applies to appvoyer as well.
> 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 20m
> 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)
