CI: migrate from travis-ci.org to travis-ci.com

[jorisvandenbossche]

See https://docs.travis-ci.com/user/migrate/open-source-repository-migration, if we want to keep the Travis CI builds, we need to migrate to the .com version before the end of the year.

[jorisvandenbossche]

(I am adding the 1.2 milestone for now. Not that it is in any way linked or a blocker to actually releasing 1.2, but doing that as a way to keep this issue a bit more visible, and the timeframe we need to do this migration also is somewhat similar as the planned timeline for 1.2)

[erfannariman]

Just for my understanding, on the long term, is it needed to keep Travis while we have the option to use Azure pipelines and/or GitHub Actions?

[jreback]

not all capabilities are currently supported in azure, mainly the database testing
also travis has arm and usually is easier to do builds like numpy dev

[erfannariman]

not all capabilities are currently supported in azure, mainly the database testing
also travis has arm and usually is easier to do builds like numpy dev

Thanks for the clarification.

[simonjayhawkins]

I think the gist of the discussion in scipy/scipy#13109 is that there is a preference to migrate to Azure/Github Actions where possible.

not all capabilities are currently supported in azure, mainly the database testing
also travis has arm and usually is easier to do builds like numpy dev

We currently have 4 build in Travis. Do all of these need to be on Travis?

[simonjayhawkins]

(I am adding the 1.2 milestone for now. Not that it is in any way linked or a blocker to actually releasing 1.2, but doing that as a way to keep this issue a bit more visible, and the timeframe we need to do this migration also is somewhat similar as the planned timeline for 1.2)

because of potential issues with credits, it may be worth leaving this to the last minute scipy/scipy#13109 (comment)

[fangchenli]

We currently have 4 build in Travis. Do all of these need to be on Travis?

GitHub Actions have SQL services. We could migrate the 3 builds that require databases to GitHub Actions.

[jorisvandenbossche]

GitHub Actions have SQL services. We could migrate the 3 builds that require databases to GitHub Actions.

I think it would certainly be very welcome if someone can look into setting up database tests elsewhere (such as github actions)

[simonjayhawkins]

(I am adding the 1.2 milestone for now. Not that it is in any way linked or a blocker to actually releasing 1.2, but doing that as a way to keep this issue a bit more visible, and the timeframe we need to do this migration also is somewhat similar as the planned timeline for 1.2)

The 1.2.x branch will be active past the deadline, so any changes needed as part of the migration will need to be backported. (so keeping this issue on the 1.2 milestone is fine.)

[fangchenli]

After #38344, the only build left on Travis is arm64.

[jreback]

ok i did this migration. let's see what happens.