Migrate scala/* repos from travis-ci.org to travis-ci.com

[SethTisue]

as per https://mailchi.mp/3d439eeb1098/travis-ciorg-is-moving-to-travis-cicom , we need to do this before the end of 2020

migrating is super easy: https://docs.travis-ci.com/user/migrate/open-source-repository-migration/#the-migration-steps

[SethTisue]

a little while ago I went to https://travis-ci.com/organizations/scala/migrate and migrated almost every scala/* repo

I intentionally left out our most critical repos: scala/scala, scala-dist, scala-dist-smoketest. I figured we could get them in a second round later, if the first round seems okay. I see travis-ci.org references in scripts/common and README.md. we might want to wait until after 2.12.13 and 2.13.4 are both out

can anyone think of anywhere else we'll need to update any links or anything?

[SethTisue]

@sjrd could the Scala Center and/or LAMP take care of docs.scala-lang, scala.epfl.ch, scala-lang, and vscode-scala-syntax?

[sjrd]

Yes, that shouldn't be a problem.

[lrytz]

scala/scala, scala-dist, scala-dist-smoketest

we'll need to fix some scripts there

https://github.com/scala/scala/blob/30fd6009669171f7dc36af57aa045fa4ac821c97/scripts/common#L187

https://github.com/scala/scala-dist/blob/4218dfc75b9e2a5310b7abde28d3d6ba8e611601/scripts/common#L17

https://github.com/scala/scala-dist/blob/4218dfc75b9e2a5310b7abde28d3d6ba8e611601/admin/build.sh#L65

https://github.com/scala/scala-dist-smoketest/blob/1ea1d58dcf914db7ae1ac3b0202c5b6d68c2a29a/scripts/common#L16

[lrytz]

We probably want to migrate scala/scala after the upcoming releases.

[SethTisue]

@ignasi35 points out that branch protection rules may need to be updated when a repo is migrated

[sjrd]

Ouch, new pricing model for Travis, which also impacts the free OSS usage:
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

It's bad. I believe this means we'll have to migrate to something else instead, perhaps GitHub Actions.

[SethTisue]

Perhaps we needn’t be so pessimistic so soon. The blog post makes reference to abuse — you can imagine people doing Bitcoin mining or whatever under cover of OSS. We’re an established, reputable organization — I think there’s a strong chance that if we asked they’d say “yes of course, you’re exactly who we want to support” with free runs.

There might be other reasons to ultimately migrate, but I think it’s at least worth asking, so then we wouldn’t be under any time pressure.

[dwijnand]

I think while we're haven't migrated, we're not burning those precious 1000 minutes. So we shouldn't migrate until we know that Travis CI is happy for our builds to continue to run on their service, as an OSS project.