Migrate builds from travis.org to travis.com about akka-meta HOT 22 CLOSED

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

from akka-meta.

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?

from akka-meta.

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

from akka-meta.

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

from akka-meta.

Migrating

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

from akka-meta.

migrating:

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

from akka-meta.

Hmm, either we broke something of the Travis migration tool from travis-ci.org to travis-ci.com just destroyed our settings for branch protection.

See, for example, how akka-paradox or akka-grpc-quickstart-scala.g8 no longer have either a Travis CI or a Lightbend CLA validator rules.

edit: hmmm, but my test PR run both CLA and Travis CI checks

from akka-meta.

Note to self: none of the repos migrated before this comment have the branch rule protections completely reviewed.

from akka-meta.

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.

from akka-meta.

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

from akka-meta.

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.

from akka-meta.

Migrating akka-grpc

from akka-meta.

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

from akka-meta.

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

from akka-meta.

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.

from akka-meta.

I'm migrating akka/akka-management

from akka-meta.

I'm migrating akka/akka-grpc-sample-kubernetes-scala

from akka-meta.

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

from akka-meta.

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

from akka-meta.

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.

from akka-meta.

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.

from akka-meta.

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

from akka-meta.