![]() hours! On Bitrise we would need to contact support to get pricing for more than 50,000 credits, but based on known prices we could assume that it would cost around $8,000! Xcode Cloud biggest plan is available $399. We will need to buy a 30,000 credits package having a Teams plan, in total $1,350.00! It’s 30x more than Xcode Cloud! This is a huge difference! On Bitrise we will need 100*60*4 credits = 24,000 credits, assuming the average machine “8vCPU 35 GB RAM running on Intel Mac Minis”. Xcode Cloud 100 hours plan costs $44.99/month. Let’s compare it to Bitrise which is another great and mature solution for mobile CI/CD. However, let’s assume that our large project is using 250 hours/month. First of all, you get 25 hours/month for free until December 2023. Priceįor now, Xcode Cloud has very competitive plans. Also, the environment is dedicated to Apple apps, so we can expect that build performance will be increasing with time. Future developmentįor now, Xcode Cloud is very simple, but I assume that Apple will present new features soon. We can quite reasonably assume that Xcode Cloud will get a day one support for every new platform feature, beta system, and beta simulator. Once you set up Xcode Cloud, all your team members added to the project will automatically get access to see and run builds in Xcode. If you have ever set up CI/CD, you know what I am talking about :D. You don’t have to generate API keys, export certificates, go from door to door to find the person who’s got a distribution certificate, etc. You can instantly build your project and release it to TestFlight and App Store. Now you just add Xcode Cloud to your project and it gets automatically access to all provisioning profiles and certificates. SimplicityĪnother important thing is the simplicity of the configuration. We don’t need extra tools to format test results etc. Test results are displayed in the same way, we can see logs and warnings as if we run the build locally. Xcode Cloud gives also a similar experience to our daily work with Xcode. ![]() This is a really significant advantage, it provides a smooth experience without leaving Xcode. You can even see snapshots from your tests and rebuild branch. You can check your builds, change workflows, check which test failed and navigate directly to its source code. Now you can see your CI/CD system directly in Xcode. ![]() And this is what Apple gives us with Xcode Cloud. Why Xcode Cloud is worth trying outĪs we all know, it is very comfortable to have everything built into one ecosystem. If not please at least take a look at my post: Xcode Cloud – overview & setup. I assume that you have a general idea of how Xcode Cloud works and what it offers. In this post, I will share my thoughts and the problems I encountered. I recently had the opportunity to try migrating a large commercial project to the Xcode Cloud for testing purposes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |