Alternatively we could apply for (recurring) Travis-CI credits for our
OSS project:
This might be the easiest way to mitigate this for now.
>From the Travis CI article:
* 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.
Please include:
* Your account name and VCS provider (like travis-
ci.com/github/[your account name] )
* How many credits (build minutes) you’d like to request (should
your run out of credits again you can repeat the process to
request more or discuss a renewable amount)
On November 20, 2020, Matt Sicker <boa...@gmail.com> wrote:
> If use of Kubernetes in CI is useful here, there's a thread on
> bui...@apache.org right now planning how to go about doing so. Note
> that GitHub Actions are also somewhat rate-limited across the ASF, so
> we might need some hybrid CI solutions depending on how long or
> frequently things are running. Moving from Travis is a good idea
> either way as it's even more rate-limited.
>
> On Fri, 20 Nov 2020 at 09:24, Carlos Santana <csantan...@gmail.com>
> wrote:
> >
> > Thanks for bringing it Martin
> >
> > Our current usage of Travis for OpenWhisk we use the ASF foundation
> > account, and Infra pays some amount $ to able to support so many
> builds by
> > many Apache projects.
> >
> > With that said I think the amount paid today might not cover all the
> builds
> >
> > I have used GitHub actions and I would +1 for OpenWhisk to move away
> from
> > Travis
> >
> > Github Actions are event driven you can have one action in one repo
> trigger
> > another one in another repo we can leverage this
> >
> > If you are going to get started don’t reinvent the wheel there are
> many
> > actions available in the open market place, things like reviewdog
> >
> > And avoid code duplication you can have the action definitions for
> > OpenWhisk specifics in a central repo and reference them from the
> other
> > repos
> >
> > —Carlos
> >
> > On Fri, Nov 20, 2020 at 10:15 AM Martin Henke <martin.he...@web.de>
> wrote:
> >
> > > Hi,
> > >
> > > free Travis usage will be ending for open source projects end of
> the year.
> > >
> > > See:
> > > https://mailchi.mp/3d439eeb1098/travis-ciorg-is-moving-to-travis-
> cicom
> > > https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
> > >
> > > Open source projects will migrated to trial accounts in travis-
> ci.com
> > > with some free budget.
> > >
> > > > 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).
> > >
> > > It looks like our OW projects have to find other alternatives like
> GitHub
> > > Actions.
> > >
> > > Kind regards,
> > > Martin
> >
> > --
> > Carlos Santana
> > <csantan...@gmail.com>
