Needs advice
on
Jenkins
Travis CI
and
CircleCI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

READ LESS
3 upvotes·121K views
Replies (6)
Recommends
Travis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

READ MORE
3 upvotes·119.3K views
Developer at Elegant Themes·

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

READ MORE
13 upvotes·1 comment·197.8K views
Vlad Khazin
Vlad Khazin
·
April 19th 2019 at 10:07PM

I prefer CircleCI over Jenkins for the following reasons:

1. each repo has an isolated build container - no web of dependencies to manage

2. no ocean of plugins to configure - all what you need is the yaml file and, maybe, in a custom build image

3. decentralized execution of builds - no master/agents complexity

·
Reply
View all (6)
Avatar of akarsh3007