[vishnu_ks]

The main reason why we moved to CircleCI was due to the rising test flakes and outages in TravisCI. Also, TravisCI comes with a lot of crap pre-installed which can be a pain sometimes. With CircleCI you can provide your own custom Docker image for running the build. If the build fails there is even an option to SSH into the build to debug. This issue has a lot of details on what it takes to migrate an open source project from Travis CI to CircleCI if you are interested. https://github.com/zulip/zulip/issues/7748

[jfaat]

You can ssh and debug a travis build as well

[blueyed]

But only on travis-ci.com, not for Open Source (.org) IIRC.

[DrTorte]

(Disclosure: Travis CI Employee)

We can do it on .org as well! Just need to reach out to us via email to enable it (as well as the instructions, as it requires a manual API call rather than a UI Button.) And, as Involans also mentioned, we are merging the two together.

[e-mail] And we'll set you right up with debug mode. :)

[ivan4th]

There used to be a catch, though, don't know if it's already fixed. If you use this ssh debugging feature you make your secrets world-accessible (anyone can connect to ssh and grab them). This was one of the reasons why I switched to CicleCI, actually (besides their Workflows).

[DrTorte]

Yes, it is indeed correct that if somebody grabs the ssh command with the key while you are debugging, it is accessible. It's something that we want to address in a better way, but other priorities are present right now (build image updates, performance improvements, some new features that we haven't announced yet.) Still, the feedback is appreciated!

[involans]

You do realise that the two platforms are being merged, with .org projects being migrated to .com?