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

Move from Travis CI to GitHub Actions #1559

Closed
HonkingGoose opened this issue Jan 5, 2021 · 3 comments · Fixed by #1616
Closed

Move from Travis CI to GitHub Actions #1559

HonkingGoose opened this issue Jan 5, 2021 · 3 comments · Fixed by #1616

Comments

@HonkingGoose
Copy link
Contributor

The Travis CI on the .org domain is shutting down very soon.
After the shutdown no tests will run on pushes to master or when PRs are opened that target master.

Travis suggest that you migrate to their offering on the .com domain. You get a one-time 1000 minutes of build time. After the free one time credit is used up, you can apply to open source plan where "upon validated request you may receive free OSS credits for your public builds".

Quote from https://www.travis-ci.com/plans

Free for open source. We love the Open Source Community, and to show how much we love it, upon validated request placed with our Support Team you may receive free OSS credits for your public builds.

I think the easiest thing is to migrate to GitHub Actions, as those are free for public repositories, with no strings attached.

GitHub docs on migrating from Travis to GitHub Actions

@pedrorijo91
Copy link
Member

I think it may be easier just to ask for free credits. but if anyone wants to work on the migration for github actions it would be ok as well

cc @peff it seems we need an admin on this:

@peff
Copy link
Member

peff commented Jan 6, 2021

I'd rather move to Actions, as the experience seems better to me (I may be biased, though). Specifically, I've seen cases where the Travis jobs are queued for a half hour or more, which holds up further movement on a PR.

I also haven't found our tests to be all that helpful in general, as they really just render a couple of pages (and it looks like there's a ton of stale inactive tests, too!). They were helpful with the ruby/rails transition recently, but the vast majority of changes we do are in the rake jobs that pull in book and manpage content, and those aren't covered at all (good tests there would be quite a bit trickier, as it's a bit expensive to do a full import; we might be able to get by with a single static version or something).

@pedrorijo91 pedrorijo91 changed the title Travis CI .org domain shutting down, CI will stop working Move from Travis CI to Github Actions Jan 6, 2021
@pedrorijo91 pedrorijo91 changed the title Move from Travis CI to Github Actions Move from Travis CI to GitHub Actions Jan 6, 2021
@jnavila
Copy link
Contributor

jnavila commented Jan 6, 2021

Plus we really need some reliable test (see #1561)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants