Why do Atom, VSCode or Ava use more than one continuous integration services?

1

Continuous integration services, like Travis, CircleCI or AppVeyor have been proofed to be really useful to make sure that the project is working as intended automatically.

But why do some repositories use more than one CI?

Doesn't one already do the job well? Is it to prevent a service or two not working as intended or down at some point?

For example:

Atom (3): CircleCI, Travis, AppVeyor
VScode (2): Travis, AppVeyor
Ava (2): Travis, AppVeyor
Vapor (2): Travis, CircleCI

Update:

React made the switch from TravisCI to CircleCI long time ago.

https://github.com/facebook/react/pull/8486

For context, we're interested in moving over to CircleCI for now because our Travis queue for the /facebook org on GitHub is perpetually hours behind. On the other hand, Circle builds are able to start almost instantaneously.

Is this related to why big projects use several CI services?

zurfyx

Posted 2017-01-17T18:57:44.737

Reputation: 95

Why is this question on SuperUser? this is a programming question. – Mark Arnott – 2017-01-27T15:16:39.510

@MarkArnott I don't think so. I didn't provide nor I expect code in the answer. What's more, Git, GitHub and repository can be used for both code and other non-programming stuff. – zurfyx – 2017-01-27T15:30:38.623

Answers

3

They can often do different jobs:

  • Travis supports Linux and macOS, but currently not Windows.

  • Circle CI seems to support macOS more reliably than Travis.

  • AppVeyor supports only Windows, and it can do additional tasks – e.g. generate the "installer" packages for releases.

user1686

Posted 2017-01-17T18:57:44.737

Reputation: 283 655

Asked: 2017-01-17T18:57:44.737

Viewed: 160 times

Active: 2017-01-27T14:49:11.260