Or while deployment will be ongoing, you won’t be able to operate anything because of the installed dependencies.Īlso, you can’t just launch several tasks on one runner without preparation and a couple lines of code. If anyone decides to deploy CI for another project, they can easily use any new dependency to crash your whole CI/CD. Quite easy, isn’t it? There’s a big downside, though. It takes 3 minutes to build the project, and it takes 9 more minutes to build it and upload to App Store Connect. We use Mac Mini 2018, 6-core Intel Core i7, 16 GB RAM. After that, you can register runners and launch a pipeline. When launching a build, we use Python scripts to input build info into the repository, and we also change the task status in the task tracker. Also, on the local machine you can install any necessary dependencies, which is important for us. The only thing you need to do is install Xcode Command Line Tools, rbenv, Fastlane, and Gitlab Runner. It’s a convenient, but not very reliable way. You can buy and place a Mac Mini in the office. To estimate time for the completion of the tasks, let’s take a project that has been developed for almost 2 years and has 20 Cocoapods dependencies, including Rx, Realm, Firebase, Swinject and others. We researched possible deployment options and compared how easy and how long it takes to configure, use and scale: In this article, we’ll look at all possible solutions we found for the deployment of Gitlab CI/CD on a device and in the cloud. First we thought of Docker, but there was neither enough info about it nor any other possible ways. After our IOS department deployed our CI/CD on a Mac Mini, we got an idea of scaling and encapsulating it. Hey, Habr! I’m Yaroslav Fomenko, Doubletapp iOS-developer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |