ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "jaruga (Jun Aruga) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "jaruga (Jun Aruga)" <noreply@ruby-lang.org>
Subject: [ruby-core:117033] [Ruby master Misc#20013] Travis CI status
Date: Fri, 01 Mar 2024 15:54:26 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-107101.20240301155426.11018@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20013.20231121141056.11018@ruby-lang.org

Issue #20013 has been updated by jaruga (Jun Aruga).


I found the following information on https://www.traviscistatus.com/ . Travis CI is undergoing a maintenance in a week of 27/Feb - 5/Mar.

> Back-end maintenance 27-Feb to 5-Mar
> 
> Update - Build status on GitHub works. Builds triggered from GitLab, BitBucket and Assembla operational. Next updates on Feb-29.
Feb 28, 2024 - 12:42 UTC
> 
> Update - Be advised: Build statsues are not passed back to GitHub after build is executed. Triggering builds from GitLab, BitBucket and Assembla not available. We are in progress with maintenance activities.
Feb 28, 2024 - 11:36 UTC
> 
> In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 27, 2024 - 08:00 UTC
> 
> Update - Reminder: Travis CI will be undergoing a maintenance in a week of 27/Feb - 5/Mar. There may be intermittent service detoration, particularly on Feb 28th.
Feb 27, 2024 08:00 - Mar 5, 2024 08:00 UTC
> 
> Scheduled - Travis CI will be undergoing a maintenance in a week of 27/Feb - 5/Mar. We will do all that we can to not interrupt the service during this period. If you spot erratic or deteriorated service behavior please report back to our support.
Feb 27, 2024 08:00 - Mar 5, 2024 08:00 UTC



----------------------------------------
Misc #20013: Travis CI status
https://bugs.ruby-lang.org/issues/20013#change-107101

* 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/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/

  parent reply	other threads:[~2024-03-01 15:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 14:10 [ruby-core:115438] [Ruby master Misc#20013] Travis CI status jaruga (Jun Aruga) via ruby-core
2023-11-21 14:12 ` [ruby-core:115439] " jaruga (Jun Aruga) via ruby-core
2023-11-22 11:20 ` [ruby-core:115450] " jaruga (Jun Aruga) via ruby-core
2023-11-22 12:52 ` [ruby-core:115451] " jaruga (Jun Aruga) via ruby-core
2023-11-22 13:06 ` [ruby-core:115452] " jaruga (Jun Aruga) via ruby-core
2023-11-22 13:31 ` [ruby-core:115453] " jaruga (Jun Aruga) via ruby-core
2023-11-22 15:55 ` [ruby-core:115456] " jaruga (Jun Aruga) via ruby-core
2023-11-22 16:30 ` [ruby-core:115457] " jaruga (Jun Aruga) via ruby-core
2023-11-23 14:07 ` [ruby-core:115464] " jaruga (Jun Aruga) via ruby-core
2023-11-23 23:49 ` [ruby-core:115467] " jaruga (Jun Aruga) via ruby-core
2023-11-24  8:37 ` [ruby-core:115473] " jaruga (Jun Aruga) via ruby-core
2023-11-24 13:31 ` [ruby-core:115475] " jaruga (Jun Aruga) via ruby-core
2023-12-22 19:33 ` [ruby-core:115872] " jaruga (Jun Aruga) via ruby-core
2024-01-30 12:46 ` [ruby-core:116505] " jaruga (Jun Aruga) via ruby-core
2024-01-30 14:33 ` [ruby-core:116509] " jaruga (Jun Aruga) via ruby-core
2024-01-30 19:48 ` [ruby-core:116515] " jaruga (Jun Aruga) via ruby-core
2024-01-30 23:41 ` [ruby-core:116519] " jaruga (Jun Aruga) via ruby-core
2024-01-31  8:57 ` [ruby-core:116524] " jaruga (Jun Aruga) via ruby-core
2024-02-23 22:00 ` [ruby-core:116918] " jaruga (Jun Aruga) via ruby-core
2024-02-23 22:57 ` [ruby-core:116920] " jaruga (Jun Aruga) via ruby-core
2024-02-24  9:01 ` [ruby-core:116925] " jaruga (Jun Aruga) via ruby-core
2024-02-24  9:08 ` [ruby-core:116926] " jaruga (Jun Aruga) via ruby-core
2024-02-24 19:17 ` [ruby-core:116929] " Eregon (Benoit Daloze) via ruby-core
2024-03-01 12:18 ` [ruby-core:117029] " jaruga (Jun Aruga) via ruby-core
2024-03-01 12:33 ` [ruby-core:117030] " jaruga (Jun Aruga) via ruby-core
2024-03-01 15:54 ` jaruga (Jun Aruga) via ruby-core [this message]
2024-03-04 12:23 ` [ruby-core:117048] " jaruga (Jun Aruga) via ruby-core
2024-03-04 12:28 ` [ruby-core:117049] " jaruga (Jun Aruga) via ruby-core
2024-03-05 20:53 ` [ruby-core:117058] " jaruga (Jun Aruga) via ruby-core
2024-03-06 16:40 ` [ruby-core:117066] " jaruga (Jun Aruga) via ruby-core
2024-03-21 17:33 ` [ruby-core:117284] " jaruga (Jun Aruga) via ruby-core

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-107101.20240301155426.11018@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    --cc=ruby-core@ml.ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).