Skip to content

Rethinking CI? #362

@junaruga

Description

@junaruga

(I posted this topic on the MySQL Ruby binding mysql2: brianmario/mysql2#1149 .)

Do you know the Travis following announcements about their changes?
https://blog.travis-ci.com/oss-announcement
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

The upcoming pricing change will affect those of you who are:
Building on a public repositories only

When I am running ruby-pg Travis CI on my forked repository now, it is very slow now. It takes time to even start. You can see the log.

I see the Ruby project recently migrated the most cases to GitHub Actions remaining a few non-x86_64 jobs in Travis.
https://github.com/ruby/ruby/blob/f3c19ddfbcfde63505a34b7a5b3a640f23b22dc0/.travis.yml#L199-L204

So, what do you think about migrating our CI from Travis to GitHub Actions or an alternative CI?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions