Negative Credit balance on Travis CI, unsure what to do?

[rnag]

• Cookiecutter version: 1.7.3
• Python version: 3.9
• Operating System: Mac OS Catalina (10.15.7)

Description:

I've been using Travis CI to run automated tests (only occasionally) for my public Github repos for a month or two, but now I suddenly noticed that CI builds via Travis were not getting triggered for PRs that I opened.

I was a little confused, and went to check the Travis CI page when I saw the a message telling me I had a negative credit balance in my account (added screens below). I was completely blindsided by this, and for some reason assumed Travis CI would be free for commerical use on public GH repos; I also only occasionally run CI builds, each of my builds runs for maybe a minute and probably only run like 10 builds in a week at most.

But now it looks like I have to actually spend money to continue running automated test builds? I'm a little confused but if i'm understanding it correctly I'll have to end up spending 60$/month for a subscription now? I generally hate taking on new subscriptions because I feel it's like a monthly commitment that you'll never get out of. However I unfortunately feel like my CI builds are now suddenly being held hostage unless I spend money out of my wallet to resolve the issue, which is kind of a strange situation to be in.

So my question was, has anyone else run into the same thing I have below (maybe through only occasional use of CI builds)? Wondering if there is any other potential CI solution that potentionally will help me to avoid a monthly subscription if possible. Because i'm not really not good at managing my financials, and a few months down the lane it might have completely slipped my mind what subscriptions I currently have active. I did notice that someone else mentioned Github Actions as a possible CI alternative, but I'm not sure if it's exactly a drop-in replacement for Travis? I'm very happy with Travis CI because it allows me to run parallel builds for different Python versions, and the builds are also really fast (less than a min or so on average). Looking for any suggestions that may help point me in the right direction. Thanks.

Note: the "other" user below is the PyUp bot, which automatically creates PRs when there are any new versions of my project dependencies available.

[PsiACE]

I'm not sure, but maybe we can try switching ci to github actions

[rnag]

Yep, I think that might be a good idea actually. I'm not sure if Travis CI updated their billing plans lately, but looks like the free tier might be a bit limited. I was hoping my credits would refresh after a certain period of time (monthly for example) however it looks like it might not be the case.

I'm currently looking into github actions as well, but will probably need to do some tests to check if the config from Travis CI carries over. Hopefully its pretty simple to move testing environment to actions and there are no "gotchas" that I have to watch out for. I had a look at the billing criteria for github actions and it seems pretty reasonsable to me.

[rnag]

I realized I had some free time, so I finally got around to test and implement a GitHub Actions workflow on an existing repo - credits go to this repo for helping me get started. GitHub actions has a few annoying and not well-documented drawbacks based on personal testing, such as not being able to trigger a workflow on both a push to branch and on a tag at the same time (i.e. trigger on a tagged commit but only on main branch). However, for most part it looks like it is working well. I also need to modify my tox.ini file I think, since that was using references to travis, so still need to do some additional testing with it - but so far, looks like it's all going well.

I did make a few changes to the CI build process, like removing the CHANGELOG file generation and the use of poetry - unless someone explains to me what benefits this provides over a simple setup.py deployment, I'd rather not use something new and untested that might potentially break the current process I have so far.

However, all that's to say is that it would probably be a good idea to switch the CI tool used in this template to GH actions, which is blessedly free. My credit balance on Travis has not changed at all since I've posted - it still shows as all available credits used, and I'm not sure how to reset it either - I should mention I'm on the free plan as well.