The Swift Package Index Build System
- What is the Swift Package Index Build System?
- Why does a package show missing or incomplete compatibility?
- What revision is the default branch built for?
- How are packages built?
- How does the build system build with different Swift versions?
- When was a package last built?
- Is it possible to hide failing builds for unsupported platforms?
- If a build is showing failed incorrectly, how can I fix it?
- If a build is showing an error that seems unrelated to the build, how can I fix it?
- How can I diagnose problems where dependencies can't be resolved?
What is the Swift Package Index Build System?
The Swift Package Index bases its Swift version and platform compatibility data on real-world results from our build system. The build system supports all Apple platforms (iOS, macOS, tvOS, watchOS) and Linux, giving comprehensive, proven, real-world compatibility information.
The Swift Package Index polls every package for changes and new releases constantly. Whenever it sees changes, it compiles the code across a comprehensive set of Swift versions and platforms. For example, check out the package compatibility report for SnapKit.
Note: The build system checks compatibility for every release, no matter how frequent, whereas the system builds the default branch for a package at most every 24-hours. If there are updates to a default branch during the same day, new compatibility checks start once the 24-hour timeout expires.
Why does a package show missing or incomplete compatibility?
The Swift Package Index will pick up new default branch revisions and releases automatically. It can take a little while for build results to become available after a commit or new version release though, so if the compatibility matrix shows a clock symbol then builds are still pending, and results are on their way!
What revision is the default branch built for?
The Swift Package Index does not currently display which revision the default branch tracks. If a default branch revision changed more than a few hours ago, everything should be up to date. If there looks to be a problem with a build not updating after several hours, please raise an issue.
How are packages built?
The build system runs either
swift build depending on the platform and specified Swift versions.
xcodebuild, we apply some heuristics to find the correct scheme to build. If a package contains a single scheme (as reported by
xcodebuild -list), the build system will use that scheme. If
xcodebuild -list reports multiple schemes, the build system will choose the one ending in
-Package. Otherwise, it will try removing any Xcode project and workspace files and rely on SPM’s scheme discovery to autogenerate a package scheme.
How does the build system build with different Swift versions?
The build system aims to reproduce a real-world environment for building packages as much as possible. Ideally, if the Swift Package Index says it's compatible with Swift 5.1 and your project uses Swift 5.1, it should work. The most real-world way for us to build is to use multiple different versions of Xcode to process each package. We use the latest available version of Xcode that shipped with the release of Swift that we want to compile with as default.
- Swift 5.1 builds with Xcode 11.3.1.
- Swift 5.2 builds with Xcode 11.6.
- Swift 5.3 builds with Xcode 12.4.
- Swift 5.4 builds with Xcode 12.5.
- Swift 5.5 builds with Xcode 13.1.
The build system uses the
DEVELOPER_DIR environment variable to switch versions of Xcode. This applies to both
swift build commands.
When was a package last built?
The Swift Package Index does not currently display the date/time of the last build for a package, but everything is typically up to date a few hours after a revision or version release.
Is it possible to hide failing builds for unsupported platforms?
Not currently. However, by using grey rather than red for the compatibility matrix, we aim to show this is a lack of platform or Swift version support rather than a failure per se. On the build details page, we show statuses with red crosses to make it easier for the package maintainer to find and inspect what may be genuine problems.
If a build is showing failed incorrectly, how can I fix it?
As a package author, you might think that a package should be compatible with a platform or Swift version, where the Swift Package Index shows it as incompatible. First, please try to replicate the build locally with the build command that the build system uses. The build details page shows the full build command which will help reveal if there is some issue with the package set up or our way of discovering the build scheme.
If you can fix the problem, great! Fix the issue, push the change, and we will re-process your builds. If the problem is more serious, please raise an issue so we can improve the build system.
If a build is showing an error that seems unrelated to the build, how can I fix it?
In some cases, we may have encountered build issues unrelated to your package. Please confirm using the build command shown on the build details page that you can build your package successfully for a given Swift version and platform. If this succeeds, please raise an issue so we can remove the faulty builds and schedule a rebuild.
How can I diagnose problems where dependencies can't be resolved?
If you encounter the following error on the build details page:
xcodebuild: error: Could not resolve package dependencies: unknown package 'foo' in dependencies of target 'Bar'; valid packages are: 'baz', 'baq'
The likely cause is a local package dependency (for instance, an example project that imports the package) with the package dependency declared as:
In cases like this, Xcode cannot resolve package dependencies because of how it guesses package names. To fix this, specify the package name in your dependency clause, like so:
.package(name: "foo", path: "../../")
You can find more details in this issue.