From: "jaruga (Jun Aruga) via ruby-core" Date: 2024-06-10T11:51:00+00:00 Subject: [ruby-core:118266] [Ruby master Misc#20013] Travis CI status Issue #20013 has been updated by jaruga (Jun Aruga). Travis support enabled my forked repositories of ruby/ruby, ruby/zlib and ruby/prism where Travis was used. It seems that we need to submit a list of github accounts to enable someone's forked repository from ruby/* organization. Maybe they changed how to enable Travis recently. I am working to get the list of the github accounts who contributed to the ruby/ruby, ruby/zlib and ruby/prism in the last 2 years, and submit the list to Travis support to enable Travis for their forked repositories. ---------------------------------------- Misc #20013: Travis CI status https://bugs.ruby-lang.org/issues/20013#change-108764 * Author: jaruga (Jun Aruga) * Status: Open ---------------------------------------- I would like to use this ticket to manage our activities to report Travis CI status. Because there is Travis CI status page provided by Travis CI. However, even when the page shows ok, I actually see infra issues. https://www.traviscistatus.com/ I would share my activities and report the Travis CI status on the ticket. The ticket's status is not closed until we stop using Travis CI. The easiest option to fix the Travis infra issue is to email Travis CI support `support _AT_ travis-ci.com`. You can check [this ruby/ruby Travis CI wiki page](https://github.com/ruby/ruby/wiki/CI-Servers#travis-ci) for details. -- https://bugs.ruby-lang.org/