On 6/1/21 11:54 AM, Rikki Cattermole wrote:
> Hello everyone!
> 
> A little devops update, since there is a number of projects in the D-sphere that have used travis-ci.org in the past.
> 
> As per their blog post[0], they have shut down their .org domain.
> 
> What this means to us as developers is if you still use travis-ci.org for your CI rather than travis-ci.com it will no longer work and therefore checks won't pass when making PR's.
> 
> Over on the dlang-community organization, Amin Yahyaabadi (@aminya) has very kindly created a PR that replaces DCD's Travis scripts over to Github Actions. I have tested it after merging, and it is good to go!
> 
> Furthermore, if you need any admin assistance with bringing any dlang-community repository from travis-ci.org to another CI system please feel free to ping me (@rikkimax).
> 
> [0] https://blog.travis-ci.com/2021-05-07-orgshutdown

Thanks for the reminder, I went in and disabled access to travis from github for mysql-native. Just recently (last weekend) switched to github actions. I had switched to travis-ci.com, and one build used up all the credits available for free projects.

-Steve

On 6/3/21 5:01 AM, FreeSlave wrote:

> They prolonged it to June 15th.
> What's not clear to me - is CI for open repositories still as unlimited as before?

No, you get 10000 "credits"

> travis-ci.com has a new tab in profile settings, called Plan, saying I have 10000 Credits. It's not clear how these credits are spent. travis-ci.org did not imply such limits and I've never had a problem with depleting any limits.

There is a page that talks about what credits get you:

https://docs.travis-ci.com/user/billing-overview/#usage---credits

The big red flag there for me is 50 credits per Macos Minute. That gives you 200 minutes. I believe I ran out of credits for ONE BUILD of mysql-native because of this (the macos builds were kinda broken and always timed out).

> The "Repositories" tab on travis-ci.com now shows a list of my forks and repos that never had travis-ci integration, but does not show any of my repos that use travis-ci.org.
> travis-ci.com has a tab called Migrate that lists my repos previously connected to travis, however it does not allow to migrate any of them unless I sign up for beta. If they ask users to change to travis-ci.com should not it be out of beta already? What's the point of asking if it's not ready yet?

I had to sign up for the beta, and even then I had to wait a while before they added access for me.

Once you sign up, then you can add travis-ci.com as a github app, and then you can see all your history (including travis-ci.org history). It was all very confusing.

I'm not sure exactly how it works now, I've moved to github actions.

-Steve

On Thursday, 3 June 2021 at 09:01:28 UTC, FreeSlave wrote:

> They prolonged it to June 15th.
> What's not clear to me - is CI for open repositories still as unlimited as before?
>
> travis-ci.com has a new tab in profile settings, called Plan, saying I have 10000 Credits. It's not clear how these credits are spent. travis-ci.org did not imply such limits and I've never had a problem with depleting any limits.
>
> The "Repositories" tab on travis-ci.com now shows a list of my forks and repos that never had travis-ci integration, but does not show any of my repos that use travis-ci.org.
> travis-ci.com has a tab called Migrate that lists my repos previously connected to travis, however it does not allow to migrate any of them unless I sign up for beta. If they ask users to change to travis-ci.com should not it be out of beta already? What's the point of asking if it's not ready yet?
>
>
> Reading travis-ci blog does not help. It all became so unclear at this point. This page [1] does not actually explain how to migrate, but says what will migrate once migration is done.
>
> [1] https://docs.travis-ci.com/user/migrate/open-source-repository-migration

In addition to the information you've already been provided about pricing, here's a blog post where they explain the changes:

https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

They couldn't continue as they did before because that meant they were footing the bill for cryptocurrency operations. All the providers are facing the same issue: https://layerci.com/blog/crypto-miners-are-killing-free-ci/

On Thursday, 3 June 2021 at 15:08:09 UTC, bachmeier wrote:
> [snip]
>
> In addition to the information you've already been provided about pricing, here's a blog post where they explain the changes:
>
> https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
>
> They couldn't continue as they did before because that meant they were footing the bill for cryptocurrency operations. All the providers are facing the same issue: https://layerci.com/blog/crypto-miners-are-killing-free-ci/

I don't dispute that crypto mining is a concern, but I find the Travis-CI people are a little disingenuous about it. Most obviously, if people are consuming too many resources, then warn them, or queue their projects, or start banning them. If that doesn't work, then move to the pricing model but give enough credits every month so that 95% of the formerly free group won't have to worry about paying. The fact that every open source project I know of is running for the hills from Travis-CI, suggests the free credits are not generous enough.

On Thursday, 3 June 2021 at 15:41:16 UTC, jmh530 wrote:
> On Thursday, 3 June 2021 at 15:08:09 UTC, bachmeier wrote:
>> [snip]
>>
>> In addition to the information you've already been provided about pricing, here's a blog post where they explain the changes:
>>
>> https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
>>
>> They couldn't continue as they did before because that meant they were footing the bill for cryptocurrency operations. All the providers are facing the same issue: https://layerci.com/blog/crypto-miners-are-killing-free-ci/
>
> I don't dispute that crypto mining is a concern, but I find the Travis-CI people are a little disingenuous about it. Most obviously, if people are consuming too many resources, then warn them, or queue their projects, or start banning them. If that doesn't work, then move to the pricing model but give enough credits every month so that 95% of the formerly free group won't have to worry about paying. The fact that every open source project I know of is running for the hills from Travis-CI, suggests the free credits are not generous enough.

I'm not sure about the details. It's not just Travis CI though. My (limited) understanding is that they'd need a way to catch "open source projects" that slip crypto mining into the build step. It would be a constantly moving target and a neverending drain on resources, so it's easier just to get rid of free CI altogether.

On Thursday, 3 June 2021 at 13:56:32 UTC, Steven Schveighoffer wrote:
> There is a page that talks about what credits get you:
>
> https://docs.travis-ci.com/user/billing-overview/#usage---credits

FWIW, there are unlimited credits for OSS and AArch64/PowerPC/Z architectures, apparently sponsored by ARM and IBM. After the end of Shippable CI, Travis is, AFAIK, the only free CI service offering AArch64 on Linux. And thus still of relevance for LDC.