Note from the publisher: You have managed to find some of our old content and it may be outdated and/or incorrect. Try searching in our docs or on the blog for current information.

When evaluating CI options for iOS projects, Jenkins and CircleCI appear at the top of the list.

While a side by side comparison between CircleCI and Jenkins for iOS isn’t exactly possible, we’ve collected a few differences that we consider core examples why you should choose CircleCI.


1. We maintain your build image

CircleCI engineers are responsible for curating the macOS build image by adding new tools and dependencies, which means when using CircleCI you don’t have to spend your engineering resources on maintaining the build image.

Additionally, we spin up a clean box for every build, every time. We have mechanisms in place to ensure that every build runs in a clean environment—this is done to guarantee the consistency between the test runs and eliminate any state that might be influencing the outcome of your tests.

2. Flexibility of your setup

We are big fans of best practices in iOS testing, and we do our best to enable them by default in the iOS builds to make it as easy as possible to get started with the widely accepted standards.

While we encourage your team to follow those practices, we realize that mobile is not ‘one size fits all so teams can use the circle.yml file to override the parts of the default build configuration that you’d like to change.

If your team is opposed to any of the currently accepted engineering practices with iOS, we’d like to hear from you—you might be able to sway our opinion!

3. We curate the features we provide

At CircleCI we curate only the best feature proposals. This means easier onboarding and a pleasant UI, which helps your team’s performance when new team members are joining.

When we introduce a feature to CircleCI, we make it available to all kinds of projects on the platform, including Linux and Android projects. Sometimes a feature that you are using for a CircleCI iOS project is iOS specific, like automated code signing, but that’s rather an exception: most of the things that you find in the documentation are available on all builds.

4. Concurrency

Unlike Jenkins, where the concurrency you get for your iOS builds is limited to the number of Mac machines you can dedicate to the task, at CircleCI we provide you with the concurrency you need without all the trouble and overhead of maintaining multiple Macs.

5. We are constantly working on improving our platform

Previously, customers pointed out that a key benefit in choosing Jenkins for iOS was that Jenkins allowed users to keep all their data within their own infrastructure, while CircleCI did not. We’re happy to say that this is no longer the case: recently we announced beta support for on-premise iOS builds with CircleCI Enterprise. Now your team can build, test, and deploy iOS behind your firewall.

It’s quick and easy to get started with CircleCI and iOS build. CircleCI provides helpful tools such as the Jenkinsfile converter, which will help save you crucial time in getting started with CircleCI. You can sign up using GitLab SaaS, Github, or Bitbucket credentials, or you can watch our brief signup tutorial video.

Try our iOS trial for 2 weeks for free!

If you have feature requests for CircleCI for iOS or questions about anything we offer, we have a community of experts ready to answer them, and don’t forget to subscribe to our Announcements Discuss Channel or add our changelog rss to your rss readers, so you can keep up-to-date on all the new integrations and features CircleCI has to offer. We look forward to hearing from you.