Project

General

Profile

Actions
Copy link

action #80394

closed

[tools] Change the CI setup due to travis-ci.org going EOL, e.g. migrate to travis-ci.com with paid plan or migrate elsewhere

Added by okurz over 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
okurz
Category:
Infrastructure
Target version:
-
Start date:
2020-11-26
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

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:

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

Related issues 1 (0 open — 1 closed)

Related to openQA Project - action #66721: Use GitHub actions for os-autoinstResolvedokurz2020-05-12

Actions
Actions
Copy link
 #1

Updated by okurz over 3 years ago

  • Related to action #66721: Use GitHub actions for os-autoinst added
Actions
Copy link
 #2

Updated by dancermak over 3 years ago

  1. Check other CI services, e.g. github actions, circleCI, OBS, etc., for their OSS free plans and migrate

I'd suggest to go with github actions. While they are not as powerful as Travis in certain aspects (yet), there's an increasingly growing ecosystem of actions and the option to run self hosted runners is a big plus as well. Also, in contrast to other CI services, you get real VMs and not just containers (unless you want to of course), which has its perks as well.

Actions
Copy link
 #3

Updated by okurz over 3 years ago

  • Subject changed from Consider migrating travis-ci.org CI to travis-ci.com or elsewhere to Change the CI setup due to travis-ci.org going EOL, e.g. migrate to travis-ci.com with paid plan or migrate elsewhere

dancermak wrote:

Also, in contrast to other CI services, you get real VMs and not just containers (unless you want to of course), which has its perks as well.

Though it seems as if travis CI supports nested virt and github actions do not: #66721#note-11

Actions
Copy link
 #4

Updated by ybonatakis over 3 years ago

+1 for github actions but i would like to ask kindly to consider a project that i came across recently and it looks really nice with some cool features(you really have to try) and very nice community(and support in fact). I am talking about buddy.work[0] and comparing with the travis at least the prices are quite similar[1]. And if i am not wrong they are open source. at least some of their repos[2]

[0] https://buddy.works/
[1] https://buddy.works/pricing vs https://travis-ci.com/plans
[2] https://github.com/buddy-works

Actions
Copy link
 #5

Updated by riafarov over 3 years ago

PR to switch CI to github actions for os-autoinst-distri-opensuse repo https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11545

Actions
Copy link
 #6

Updated by dheidler over 3 years ago

Only run ci on master branch and on PRs - not just on every branch (even on every fork):
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11690

Actions
Copy link
 #7

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from Change the CI setup due to travis-ci.org going EOL, e.g. migrate to travis-ci.com with paid plan or migrate elsewhere to [tools] Change the CI setup due to travis-ci.org going EOL, e.g. migrate to travis-ci.com with paid plan or migrate elsewhere
Actions
Copy link
 #8

Updated by okurz almost 3 years ago

  • Status changed from Workable to Resolved
  • Assignee set to okurz
Actions
Copy link

Also available in: Atom PDF