When performing the registration process, make sure it is done in user-mode, meaning - there is no need for using sudo in front of every command.There are indeed instructions on how to do that too( so please follow them) but I do need to point out a few particularities: It is the registration of your GitLab Runner that can be confusing at certain steps. The actual installation of a GitLab runner on your Mac is quite straightforward so I do recommend following the instructions provided by our GitLab friends specifically for macOS. Explained in short - it is a service on your computer ( it could be a remote server somewhere but it will be on your Mac since you are an iOS developer which makes you special :-)) that runs a certain build and its corresponding test process which you get to set up in a special configuration file. To really get a good sense of what Runners are, you can check out GitLab’s documentation about them. Second step - installing and registering a GitLab Runner It transforms the output of your build into something way more readable. When done with the above steps, you can commit and push.Ī good idea is to get xcpretty.There is no need to share any dependency schemes. When the menu window shows up, tick the Shared box corresponding to your project’s scheme and then click the Close button.To do that, you need to open your project in Xcode and choose Product > Scheme > Manage Schemes from the tab menu. Really, really make sure that you share your project’s scheme because otherwise GitLab CI cannot locate the context it needs to build and test your project.Start of by creating your project including Unit and/or UI tests and linking it with a corresponding GitLab repository.A Mac mini running macOS Sierra 10.12.6įirst step - setting up your Xcode project.But I need to note that the greater advantage, for myself at least, of having CI is that it will make you write those damn tests you have been procrastinating. I will not go into explaining what CI/CD is, you can easily google it. But about work that is not open source? You are in luck if you are using GitLab because it comes with CI built-in for free, no matter the project. IntroductionĪs developers, young or old, junior or senior, or whatever the title, we all hear about CI/CD and the tools available - there are a lot of paid ones while others are free if your project is open source for example. Make it all spicier adding fastlane to the jam, find the link for my next article at the end of this post.

My own GitLab set-up for work as well as this post came to life thanks to Angelo Stavrow’s post from 2016.

Xcode for mac 10.12.6