Shift from Travis CI to GitHub CI Pipeline

[TheYoBots]

This is what I see on https://travis-ci.org/ (when signed out), it might be better to shift from Travis CI to GitHub CI Pipelines or anything else before Travis CI shuts down. See https://github.com/actions for GitHub CI Pipelines.

Or if I’m right to continue there requires a slight payment charge.

[vondele]

I agree we should eventually move to actions.

[snicolet]

There is an example using GitHub actions for stockfish here: #2958

[vondele]

so travis now lists this We're pushing back the shutdown date to June 15th, which is very soon, meaning we will soon be without CI unless somebody can do (or help) with the migration.

[noobpwnftw]

https://www.travis-ci.com/plans
Doesn't it have a free plan we can use?

[vondele]

that would be another option to migrate to travis-ci.com, and we should be eligible for a free plan. We could look into that if we don't have an alternative GitHub actions setup.

[ddobbelaere]

Seems the migration is nothing more than a few clicks (famous last words, I know) from a user that has administrator access to Travis CI (and possibly also GitHub if access via "GitHub Apps" for Travis CI has not been enabled yet). See https://docs.travis-ci.com/user/migrate/open-source-repository-migration/#the-migration-steps

No code changes (e.g. in .travis.yml) are involved.

[ianfab]

Seems the migration is nothing more than a few clicks (famous last words, I know) from a user that has administrator access to Travis CI (and possibly also GitHub if access via "GitHub Apps" for Travis CI has not been enabled yet). See https://docs.travis-ci.com/user/migrate/open-source-repository-migration/#the-migration-steps

No code changes (e.g. in .travis.yml) are involved.

I tried that out on my account and the migration seems to work smoothly in just a few minutes. However, Travis CI no longer has guaranteed free builds, you just get an initial amount of free credits and when they are used up you need to beg them for more OSS credits. So the migration can just buy some time for the switch to Github actions to avoid temporarily being without CI.

[ianfab]

Looks like the free credits are used up now, 07c8448 did not have Travis CI any more. Also see https://travis-ci.com/github/official-stockfish/Stockfish

Builds have been temporarily disabled for public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance or alter your Consume paid credits for OSS setting.

[snicolet]

This issue can be closed, obsoleted by #3563

[TheYoBots]

Looking at the title, wasn’t it just a basic workflow? If that’s the case, I think it would be better to keep this open till a complete workflow has been implemented.

[vondele]

what makes a workflow complete, do you have suggestions? It does replace more or less what we had with travis.

There are many things we could do, probably best as separate issues, IMO.