Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to CircleCI? #9481

Closed
ktmud opened this issue Apr 7, 2020 · 7 comments
Closed

Migrate to CircleCI? #9481

ktmud opened this issue Apr 7, 2020 · 7 comments
Labels
inactive Inactive for >= 30 days

Comments

@ktmud
Copy link
Member

ktmud commented Apr 7, 2020

My PRs have been stuck at Travis CI for a couple of days. Tried to rebase and close/reopen, still can't get the CI checks to go green---sometimes even when it has successfully built in Travis itself.

Should we consider moving to other CI tools? Almost all the popular open source projects I checked have been, or are now using CircleCI, including React, Vue.js, Gatsby, Redash, MetaBase...

A quick search on GitHub has found many GitHub projects migrated from Travis to CircleCI at some point, but seldom the other way around. There were chatters about Travis going through some hardship, too.

CircleCI offers free builds for open source projects just like Travis. They also have an official migration guide, which should make things easier.


Can those who used CircleCI before comment on their experiences?

@nytai
Copy link
Member

nytai commented Apr 7, 2020

@ktmud I believe the travis choice is due to to apache's rules. I think the main issue with travis is the limited resources for apache owned repos. If there are various other builds occuring in the apache org then things can grind to a halt and it can be quite frustrating. While CircleCi is probably better maintained than travis and their tooling and performance is likely better I'm not sure the migration would completely solve these pains

@nytai
Copy link
Member

nytai commented Apr 7, 2020

Actually, looking at your PRs it appears the issue is travis isn't updating the github status check after it passes. That's definitely a headbanger. Maybe reopen the PR in another branch?

@ktmud
Copy link
Member Author

ktmud commented Apr 7, 2020

Just created a new PR with a new branch and it's still stuck...

As @kristw mentioned to me offline, another choice is to use GitHub Actions. Indeed, it seems no Apache projects are currently using CircleCI. Some of them had CircleCI configs checked in the code, but it's not active running, at least not on GitHub.

There are some Apache projects already using GitHub Actions, including Spark, incubator-dolphinscheduler, incubator-echarts, and Groovy. It's also completely free and seems pretty easy to set up.

Should we give it a try?

@villebro
Copy link
Member

villebro commented Apr 7, 2020

@ktmud I agree that things could be better with CI right now. I don't have strong feelings about CI platforms, but anything that gets the job done quickly, reliably and is ok'ed by Apache gets my vote.

@nytai
Copy link
Member

nytai commented Apr 7, 2020

Github actions looks really promising, 👍 from me

@dpgaspar
Copy link
Member

dpgaspar commented Apr 7, 2020

+1 for github actions. We can go side by side for a while and see how it goes

@stale
Copy link

stale bot commented Jun 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive Inactive for >= 30 days
Projects
None yet
Development

No branches or pull requests

4 participants