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.

Sign up for GitHub

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

Jump to bottom

Migrate Travis CI to GitHub Apps #96

Closed
annevk opened this issue May 31, 2018 · 11 comments
Closed

Migrate Travis CI to GitHub Apps #96

annevk opened this issue May 31, 2018 · 11 comments

Comments

@annevk
Copy link
Member

annevk commented May 31, 2018

I noticed GitHub services is being deprecated and no longer supported in October. I plan to follow https://docs.travis-ci.com/user/legacy-services-to-github-apps-migration-guide/ to migrate our current Travis CI usage.

If anyone knows of any gotchas with this, please let me know.
@foolip foolip mentioned this issue May 31, 2018
Closed
@annevk
Copy link
Member Author

annevk commented Sep 26, 2019

Hmm, so we haven't done this, but things still work. @foolip it seems you did this for web-platform-tests, thoughts?

@annevk annevk closed this as completed Sep 26, 2019
@annevk annevk reopened this Sep 26, 2019
@foolip
Copy link
Member

foolip commented Sep 26, 2019

I like GitHub Actions quite a bit more than Travis, but I'd recommend to wait until it exists beta in a few months since there are so many repos that have to be updated.

I'll request access to the beta for the whatwg org however, to allow experimenting before general availability.

@foolip
Copy link
Member

foolip commented Sep 26, 2019

Looks like someone already did that.

@annevk
Copy link
Member Author

annevk commented Sep 26, 2019

This is about continuing to use Travis, but as a GitHub App, because the old way supposedly was deprecated and removed. But I can't find evidence that we did any of that and things kept working...

@domenic
Copy link
Member

domenic commented Sep 26, 2019

I feel like Travis and GitHub managed to work together to effect a transparent migration. That kind of makes sense given how widespread Travis usage is.

@foolip
Copy link
Member

foolip commented Sep 26, 2019

Oh, sorry.

Yes I migrated from travis-ci.org to travis-ci.com for web-platform-tests, and it was fairly smooth. The main difference is it might change from using the old Statuses API to the new Checks API, which will change the name of the checks and require all branch protection rules to be updated. Also any existing PR would then have to be trigger CI again.

I wouldn't really recommend moving to travis-ci.com unless we're sure we'll stay on Travis for a long time and not migrate to GitHub Actions.

@annevk
Copy link
Member Author

annevk commented Sep 26, 2019

I guess I'm going to close this then.

@annevk annevk closed this as completed Sep 26, 2019
@annevk
Copy link
Member Author

annevk commented Jun 9, 2020

Per https://docs.travis-ci.com/user/migrate/open-source-repository-migration this is still in beta so we should probably hold of for now, but given that the experience is more integrated with GitHub we should keep it in mind (or investigate a move to GitHub Actions I suppose, which is out of beta now I think).

@annevk annevk reopened this Jun 9, 2020
@foolip
Copy link
Member

foolip commented Jun 9, 2020

At this point I would recommend migrating to GitHub Actions. It would be a fair bit of work since the CI steps aren't uniform between repos, however.

@foolip
Copy link
Member

foolip commented Jun 11, 2020

I've filed #173.

@annevk
Copy link
Member Author

annevk commented Jun 15, 2020

Closing in favor #173 as that seems pretty close and I don't see us looking back.

@annevk annevk closed this as completed Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@foolip @domenic @annevk