From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] New Travis pricing, are we affected?
Date: Mon, 23 Nov 2020 05:55:41 +0100 [thread overview]
Message-ID: <20201123045541.1chuBwELNeGWgPKkKm7b19OHKZtjYj5Su91tQjqds1o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26120@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
Closed issue by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/26120
Description:
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
> For those of you who have been building on public repositories (on travis-ci.com, with no paid subscription), we will upgrade you to our trial (free) plan with a 10K credit allotment (which allows around 1000 minutes in a Linux environment).
> You will not need to change your build definitions when you are pointed to the new plan
>When your credit allotment runs out - we’d love for you to consider which of our plans will meet your needs.
>We will be offering an allotment of OSS minutes that will be reviewed and allocated on a case by case basis. Should you want to apply for these credits please open a request with Travis CI support stating that you’d like to be considered for the OSS allotment.
prev parent reply other threads:[~2020-11-23 4:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 23:58 [ISSUE] " Anachron
2020-11-04 1:27 ` ericonr
2020-11-04 10:28 ` Anachron
2020-11-05 6:02 ` uzr123x
2020-11-05 6:04 ` uzr123x
2020-11-05 6:05 ` uzr123x
2020-11-05 11:05 ` Anachron
2020-11-05 13:09 ` ericonr
2020-11-08 0:05 ` anjandev
2020-11-08 0:40 ` Duncaen
2020-11-08 0:45 ` anjandev
2020-11-08 0:50 ` Duncaen
2020-11-23 4:55 ` ericonr
2020-11-23 4:55 ` ericonr [this message]
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201123045541.1chuBwELNeGWgPKkKm7b19OHKZtjYj5Su91tQjqds1o@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).