-
Notifications
You must be signed in to change notification settings - Fork 36
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
Change CI SaaS to CircleCI #39
Comments
Not in favor.
This repo has 43 commits. Those problems are very, very far away from the highest-leverage tasks that could be worked on here. Neovim project has ~10 repos. If every repo uses a different CI, that increases friction for little benefit. |
A high-leverage task, for example, would be: #29 . The benefit:cost ratio of switching CI is very low. |
@justinmk Ah, actually, I don't like TravisCI pending time. CircleCI is almost haven't pending time. That's why I suggest CircleCI. But, Neovim org using TravisCI is org spec? If so, I respect it. Feel free to close this issue. |
It's not an org spec. But there should be a good reason to change things. Changing CI has a cost. Is the cost worth the benefit? Is it the highest-leverage task that could be worked on? |
Hm, OK. You're correct. |
@zchee What do you think about https://sourcehut.org/ ? We are considering this for Nvim core repo as well. |
GitHub actions probably makes the most sense for this repo, rather than a third party. |
@justinmk make sense. I'll send PR which use the GitHub action. |
@justinmk but I didn't repo owner, so can't set secrer env. any idea? |
you are on the "golang" team, and all members in that team have "Admin" role on can you access this page: https://github.com/neovim/go-client/settings Else contact me and I can create the secret at |
@justinmk Ah! I'd mistaken. I can see that URL. |
We switched to GitHub Actions. close. |
Now, Travis CI is de-fact SaaS CI. But recently, CircleCI also useful and some improved for the golang testing environment.
I think would be better to switch to CircleCI, because not job pending, faster run testing or etc.
What do you think about it? AFAIK, my company was a switch to CircleCI, As a result, increase build time to x10~x30.
Also, I have much knowledge of CircleCI features.
The text was updated successfully, but these errors were encountered: