Migrate builds from travis.org to travis.com

[ignasi35]

A quick call at the travis API lists the following repos in --org:

$ travis whatsup --org | sort

• akka/akka
• akka/akka-grpc
• akka/akka-grpc-quickstart-java.g8
• akka/akka-grpc-quickstart-scala.g8
• akka/akka-grpc-sample-kubernetes-scala
• akka/akka-http
• akka/akka-http-quickstart-java.g8
• akka/akka-http-quickstart-scala.g8
• akka/akka-management
• akka/akka-paradox
• akka/akka-persistence-cassandra
• akka/akka-persistence-dynamodb
• akka/akka-quickstart-java.g8
• akka/akka-quickstart-scala.g8
• akka/akka-sample-cluster-docker-compose-java
• akka/akka-sample-cluster-docker-compose-scala
• akka/akka-sample-cluster-kubernetes-dns-java
• akka/akka-sample-cluster-kubernetes-java
• akka/akka-sample-cluster-kubernetes-scala
• akka/akka-samples
• akka/akka.io
• akka/alpakka-kafka
• akka/akka-stream-contrib (raised Migrate from travis.org to travis.com akka-stream-contrib#184)
• akka/akka-distributed-workers-scala.g8 archived
• akka/akka-minion
• akka/akka-persistence-couchbase
• akka/akka-persistence-jdbc
• spray/spray-json

For each of the repos above the following steps are required:

1. check the webhook and branch protection rules of the repo in GitHub (make sure you keep notes on the list of branch regexp and list of checks for each rules)
2. make sure the repo has the TRavisCI Integration (e.g. https://github.com/akka/akka-grpc/settings/installations) since that will replace the travis webhook
3. go to https://travis-ci.com/organizations/akka/migrate and migrate the repo you want
4. once migration is complete, trigger a build via creating a noop PR (edit a README.md)
5. once the build for the noop PR completes, review the branch protection rules making sure all the appropriate branches have the CLA and the travis build checks enabled
6. remove the webhook for travis-ci.org

The migrate process is documented in https://docs.travis-ci.com/user/migrate/open-source-repository-migration/

NOTE: the problem is the GitHub UI will only let you select status checks from Status checks found in the last week for this repository which is why you have to trigger a noop PR. See https://github.com/akka/akka-grpc-quickstart-java.g8/settings/branch_protection_rules/new

[ignasi35]

here's the list of repos already in travis-ci.com:

$travis whatsup --com | sort
akka/akka-minion passed: #150
akka/akka-persistence-jdbc errored: #503
akka/akka-persistence-spanner passed: #349
akka/akka-platform-guide failed: #695
akka/akka-sample-cluster-kubernetes-dns-java passed: #150
akka/akka-sample-cluster-kubernetes-scala passed: #106
akka/akka-upgrade-testing passed: #382
akka/akka.io passed: #292
akka/alpakka passed: #6606

[ignasi35]

Migrating https://github.com/akka/akka-paradox

[ignasi35]

Migrating

• https://github.com/akka/akka-grpc-quickstart-java.g8
• https://github.com/akka/akka-grpc-quickstart-scala.g8

[jrudolph]

akka/akka-http

For akka-http Travis only ran Mima for all Scala versions on PR validation, so I removed that and added that to the existing Jenkins job (akka/akka-http#3577). Remaining on Travis is the master build and the release build which we might have to migrate to travis-ci.com or Jenkins.

[raboof]

Remaining on Travis is the master build and the release build which we might have to migrate to travis-ci.com or Jenkins.

... or GitHub Actions

[jrudolph]

Remaining on Travis is the master build and the release build which we might have to migrate to travis-ci.com or Jenkins.

... or GitHub Actions

No, let's try to keep it all on Jenkins where a lot of jobs regarding akka-http are running and will continue to be running.

[ignasi35]

@raboof @jrudolph let's have migration discussions in dedicated issues on each repo (e.g. akka/akka-http) linking back to this epic. :-)

[raboof]

Migrating akka-grpc

[seglo]

Migrated alpakka-kafka. PR to update project refs akka/alpakka-kafka#1246

[seglo]

I noticed that after the migration existing PRs still have an old travis-ci.org PR check. Do you have to recreate any open PRs? New PRs are fine.

i.e. akka/alpakka-kafka#1241

[raboof]

I noticed that after the migration existing PRs still have an old travis-ci.org PR check. Do you have to recreate any open PRs? New PRs are fine.

i.e. akka/alpakka-kafka#1241

I noticed that as well - they get both a .com and a .org check, right? perhaps just ignore the .org check?

[ignasi35]

I think we no longer should worry about this migration.

With the new billing plans on travis-ci.com (https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing) we'll exceed the 1000 min/month very quickly.

[ignasi35]

I'm migrating akka-persistence-cassandra and akka-persistence-dynamodb

[ignasi35]

I've reviewed the list in the description because every time I execute travis whatsup I get a completely different list.

[ennru]

I went through all our repos and all but akka-persistence-couchbase (which has issues at Travis) and akka-stream-contrib are good now.
Quite a few sample repos did not have the CLA checker, nor branch protection in place.

On a different note as the TechHub publish trigger URL changed. I updated a few but it might not be consistent, yet.

[ennru]

akka-persistence-couchbase is the only repo not migrated to travis-ci.com yet. We need help from Travis support to make that happen @johanandren is in contact with them.

[ignasi35]

I don't think there's anything left to do here.