QA » openQA Project » openQA Tests

Problem¶

CI builds on travis-ci.org are delayed longer and longer as travis CI is doing changes to the existing platform. travis CI plans to shut down active service on travis-ci.org till 2020-12-31, the platform will be read-only and only travis-ci.com will be served. But travis-ci.com is running a different billing model. There is still a "free" model and it is stated that open source projects still receive love but multiple reports state that the situation is not quite as shiny:

• https://docs.travis-ci.com/user/migrate/open-source-repository-migration#frequently-asked-questions
• https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works
• https://travis-ci.community/t/build-delays-for-open-source-project/10272
• https://travis-ci.community/t/builds-hang-in-queued-state/10250/6

also https://travis-ci.community/t/is-travis-educational-still-active-with-the-new-pricing-plan-how-to-enable-it/10456/4 explains that to be seen as a true open source project "Project must not be sponsored by a commercial company or organization (monetary or with employees paid to work on the project)" which might impact us. Though pure "educational" projects seem to be offered the true OSS allotment, see https://travis-ci.community/t/builds-fully-hanging/10613/4 . Unlike on travis-ci.org the free model on travis-ci.com offers a monthly budget of 10k credits which is likely consumed by runs of os-autoinst-distri-opensuse within a couple of hours or days within each usual month. There are official announcement updates like https://blog.travis-ci.com/oss-announcement but they do not provide more specific answers than other forum posts or quoted email responses.

Proposals¶

1. Wait how the situation evolves and just cope with longer travis CI run times until it eventually might stop working, then we decide
2. As travis CI with a support request if https://github.com/os-autoinst/os-autoinst-distri-opensuse/ wil be accepted as an "open source" project and receive enough credits to ensure below-hour CI build times over each complete month
3. Convince SUSE to pay for a paid account on travis-ci.com providing enough credits
4. Check other CI services, e.g. github actions, circleCI, OBS, etc., for their OSS free plans and migrate
5. Ask SUSE to pay for other CI and migrate there
6. Select a CI that supports "local runners", get the ressources sponsored by SUSE, include that in the CI