Migrate Travis CI from Travis-CI.org to Travis-CI.com

[abitmore]

Travis-CI.org will be shut down on December 31, 2020. Full details are in this newsletter from Travis.

Now is the time to migrate to Travis-CI.com.

Instructions for migrating to Travis-CI.com are available in the Travis documentation on repository migration.

In addition to migrating the repository to Travis-CI.com, please remember to also update the Travis status badges in the README.md files, make sure that all of the README.md files are using the Travis-CI.com badges. More information on Travis status badges is available in the Travis documentation page on status images.

Reference: https://discourse.julialang.org/t/reminder-travis-ci-org-shuts-down-on-december-31-2020/47234

[abitmore]

UPDATE: we have already consumed all credits in the free plan (see https://travis-ci.com/organizations/bitshares/plan):

Builds have been temporarily disabled for public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance or alter your Consume paid credits for OSS setting.

So simply migrating to travis-ci.com is no longer an option.

It is possible to get more credits, but I'm not sure how much work is needed.

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 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)

More info for reference:

• https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works

[bitphage]

Just migrate to Github Actions, it's already used for python-graphenelib.