CI basics with swift test and artifacts

What CI does

SUT for tests

// Example SUT and testable logic used by CI.
// In real projects, this lives in Sources/ and Tests/.
// Here we only show the code idea.

public struct Math {
    public static func add(_ a: Int, _ b: Int) -> Int { a + b }
}

print("Demo SUT ready: Math.add(2,3) =", Math.add(2,3)) // 5

Core CI commands

// Typical CI steps (illustrative):
//   swift --version
//   swift build
//   swift test --parallel
//   swift build -c release
//
// Fail fast: any non-zero exit stops the job.
print("CI steps: build → test → release build")

Create artifacts

// Create a release binary and zip it (examples):
//   swift build -c release
//   zip app-macos.zip .build/release/app
//
// Or for libraries, zip the source or attach an XCFramework if applicable.
print("Artifacts: zip files from .build/release for distribution")

Speeding up builds

Tag-triggered releases

// Release pipeline idea:
// - Trigger on tags: refs/tags/v*
// - Build & test
// - Produce artifacts
// - Upload artifacts to the release
//
// Keep the tag name consistent (e.g., v1.2.0).
print("Tip: run a special pipeline on tags to publish artifacts")

Use swift test

Recap