Pipeline configuration

Pipelines are series of preconfigured actions that can be used to automate basically every aspect of software development. Here you will learn how to configure a pipeline which builds, signs, and deploys an iOS application on a push to the selected Git branch.

Image loading...

Synchronizing repository

Click New project, switch to your Git hosting provider, and select the repository with your project:

Image loading...

Pipeline configuration

Click New pipeline and configure the pipeline details. For development pipelines, we recommend setting the trigger mode to On events > Git push. This way, Buddy will run the pipeline on every push to the selected branch:

Image loading...

Actions

Build

On the action list, switch to the Mobile tab and select the framework in which you develop your application:

Image loading...

Here we can see an Xcode action which uses Fastlane to build the application:

Image loading...

You can use the dropdown menus to change the version of your framework and select the devices to simulate:

Image loading...

Sign package

Before deploying the package, you first need to sign it. Click the + on the pipeline view and look up the Sign & Export action:

Image loading...

Here you define:

• The path to the archive created by the build action
• The export path to which the signed .ipa file will be saved
• The distribution certificate
• The provisioning profile

Image loading...

Deploy to App Store Connect

Once signed, the package can be deployed to App Store Connect. Click the + on the pipeline view and look up the App Store Publish action:

Image loading...

The action automatically detects the signed archive in the pipeline's filesystem. There you can also check the desired deployment flags:

Image loading...

Running the pipeline

With everything configured, make a push to the branch with your project: if you set the pipeline to run on Git events, Buddy will automatically fetch the repository code and trigger the pipeline.

You can check the results in the Runs tab. Here you'll find detailed logs for each action. For example:

Image loading...

Optional: Deploy using commands

Alternatively, you can deploy the package with commands directly from the build action. Here is an example for Fastlane deployment:

Image loading...

In this case, you need to upload the certificate and profile in the action's Mac OS VM tab:

Image loading...