Migrate out of Travis

[wetneb]

Thanks for running this very nice platform!
Describe the bug

It looks like Travis is no longer building pull requests or the master branch: according to https://travis-ci.com/Trustroots/trustroots, the last build was two months ago. This is probably because of the recent change of policy in Travis, which assigned a fixed amount of credits to OSS projects and stopped building them when those credits run out.

Do not be mislead by Travis' communication: they are basically closing down and do not have the capacity to support OSS projects anymore. This blog post explains it well: https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works

I had the same problem in many repositories and have been migrating them slowly to different providers. It can be quite time consuming unfortunately. There is also the option to request additional credits to Travis so that PRs keep building for some time, but in my experience it took many months before they granted my request for OpenRefine, so I am glad I migrated to something else earlier.

To Reproduce
Steps to reproduce the behavior:

1. Open a PR
2. See it does not get built

Expected behavior
The CI should run.

Additional context

There are other free CI providers: GitLab Pipelines, GitHub Actions, CircleCI, and probably many I am not aware of.

[mariha]

I was planning to migrate it to CircleCI to avoid any potential vendor lock-in and in case TR or OHN (what we've actually discussed) wanted to move to other forge, like gitea (which last time I checked was not currently supported by CircleCI either, but I guess it has greater chance to be then any other mentioned, I'd hope for the best and give it a try).

But if anyone else would like to take it, go for it!

[simison]

Thanks for outlining this! Yeah sucha bummer with Travis!

CircleCI or GitHub actions both (or some combination) work for me personally. I have good and poor experiences with both. :-) Help to write a config most welcome! Ping me on slack for access/accounts on anything you'd need.

For basic CI needs we have such small and simple needs that I'm not personally concerned what to use or that we'd get locked on anything, or spend too much time comparing alternatives, because effort of rewrite is so low. I'd just pick something and move on.

Continuous delivery pipeline is a different matter tho (we've had autodeploys to a beta server on merge) and its quite a bit more to move around. I'm not sure what's the best direction for it. In interim might make sense to not have it and prioritise fixing CI setup.

Based on experience on TR and elsewhere, a system which allows testing the PR in temporary manner seems most impactful instead of beta server. It's usually what drives the same purpose beta server is used, and more.

Anyhoo, maybe simple CI first up... 🙂

[wetneb]

I don't think I am in a good position to work on this, not having any experience with Trustroots as a developer, so the floor is yours :)

[karlkeefer]

I could attempt a circleCI integration, but not sure about setting up new accounts for the organization... Maybe someone can just invite me as collaborator to an account after creating a canonical one for the org?

I've used circleCI before, so I'd probably just attempt that.

[simison]

Sure! Does simply logging to CircleCI with your Github show Trustroots organisation there? I have some kind of TR account for CircleCI stored but not sure even how to login to it.

Worth double-checking what the free plan limits would mean to us:

Includes 2,500 free credits per week
Ability to run 1 concurrent job
Access to Linux and Windows VM builds on small and medium sizes

No idea what 2500 credits looks like in reality. 1 concurrent job sounds pretty limiting. Github actions would be entirely free (for now, of course), so there's always that as a backup if Circle seems too limited.

[karlkeefer]

Maybe a good excuse to give Actions a try 😉

…

On Thu, Oct 14, 2021, at 09:55, Mikael Korpela wrote: Sure! Does simply logging to CircleCI with your Github show Trustroots organisation there? I have some kind of TR account for CircleCI stored but not sure even how to login to it. Worth double-checking what the free plan limits would mean to us: > > Includes 2,500 free credits per week > Ability to run 1 concurrent job > Access to Linux and Windows VM builds on small and medium sizes > No idea what 2500 credits looks like in reality. 1 concurrent job sounds pretty limiting. Github actions <https://github.com/features/actions> would be entirely free (for now, of course), so there's always that as a backup if Circle seems too limited. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2389 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACKQ6GPIMK3WYV4MSXQH3TUG4DONANCNFSM5BVRUUVA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[simison]

I had just an hour-three spare and I wanted to get CI situation fixed because it's been quite frustrating.

With time constraint, I had a hunch that GitHub actions are simple and started testing it out. And oh my! This is soooo much nicer and simpler than Travis or Circle (I have quite a bit experience from both). Much less hassle with configs, secrets, keeping two services connected, etc.

I was even able to add inline linter notices. Whoa!

TODO:

• i18n string extraction CI: extract new translation strings #2438
• Eslint CI: add linter #2439
• Server tests CI: add server tests runner and disable tests #2440
• Client tests CI: Enable client-side tests and skip a single failing test #2444
• Beta deploys

[karlkeefer]

Cool 😎 will have to give Actions a closer look!

…

On Tue, Oct 19, 2021, at 14:38, Mikael Korpela wrote: I had just an hour-three spare and I wanted to get CI situation fixed because it's been quite frustrating. With time constraint, I had a hunch that GitHub actions are simple and started testing it out. And oh my! This is soooo much nicer and simpler than Travis or Circle (I have quite a bit experience from both). Much less hassle with configs, secrets, keeping two services connected, etc. I was even able to add *inline* linter notices. Whoa! TODO: * i18n string extraction #2438 <#2438> * Eslint #2439 <#2439> * Server tests #2440 <#2440> * Client tests #2440 <#2440> (kinda done but some tests were failing) * Beta deploys (didn't start on this yet) — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#2389 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACKQ6F4KW3WVIPZUGRLJSTUHXQODANCNFSM5BVRUUVA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[TMC89]

Is someone working on this last point at the moment: Beta deploys? Is it very complicated, so we're waiting for the right person? Cause it is an important tool right?