Needs advice
JenkinsJenkinsTravis CITravis CI

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?"

3 upvotes·481.9K views
Replies (6)
CTO at Cloudonix LTD.·
GitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

2 upvotes·478.6K views
Senior 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.

13 upvotes·1 comment·559.1K 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

View all (6)
Avatar of Oded Arbel

Oded Arbel

CTO at Cloudonix LTD.