Skip to main content

Managing dependencies with SPM

Abstract

On Bitrise, every Xcode Step can handle Swift package dependencies without any extra configuration. You can install and cache SPM packages easily.

Swift packages are reusable components of Swift, Objective-C, Objective-C++, C, or C++ code that developers can use in their projects. Xcode uses the built-in Swift Package Manager (SPM) to support creating and publishing Swift packages and managing package dependencies.

On Bitrise, every Xcode Step can handle Swift package dependencies without any extra configuration. For example, if you wish to build an iOS app to deploy it to the App Store, the Xcode Archive & Export for iOS Step will handle installing Swift dependencies to your app.

Installing Swift packages

You can easily install Swift packages for your iOS apps during a Bitrise build:

  1. Make sure you have correctly configured your Swift packages in Xcode.

  2. Add one of our official Xcode Steps to your Workflow. The available Steps are:

    • Xcode Archive & Export for iOS

    • Xcode Test for iOS

    • Xcode Build for testing

    • Xcode Build for Simulator

    Any of these Steps can handle the Swift package dependencies.

Caching Swift packages

With key-based caching, you only need the Restore SPM cache and the Save SPM cache Steps to cache your Swift packages. These Steps require no configuration as they automatically set up the cache keys needed for your dependencies.

Setting specific cache paths

You don't have to use the default cache paths that the dedicated key-based caching Steps use. If you need to set a specific cache path, you can do so by configuring the Save Cache and the Restore Cache Steps: Using key-based caching in your builds.

  1. Add the Restore SPM cache Step to your Workflow

    restore_spm-cache.png

    It should come before any Step that handles SPM packages in any way, such as Xcode Archive & Export for iOS.

  2. Add the Save SPM cache Step to the end of your Workflow.

In this section:

A Step is a block of script execution that encapsulates a build task on Bitrise: the code to perform that task, the inputs and parameters you can define for the task, and the outputs the task generates.

A Workflow is a collection of Steps, Environment Variables, and other configurations. When Bitrise starts a build, it runs one or more Workflows according to the configuration defined in the bitrise.yml file.