CI/CD Automated Builds
Relevant source files
The following files were used as context for generating this wiki page:
The Agent Studio MCP Engine build system automates the compilation and packaging of the application for multiple operating systems. It transforms the React-based frontend into native desktop and mobile binaries using Vite, Tauri, and Capacitor.
This system provides a unified workflow for deploying to Windows, macOS, Android, and iOS. Developers use Node.js and npm to manage the build lifecycle across all supported architectures.
Sources: BUILDING.md:3-11, package.json:7-22, README.md:10-15
Build Pipeline Architecture
The build process follows a tiered approach where web assets are generated first and then consumed by native platform wrappers.
The diagram shows the transformation from source code to final platform-specific distribution packages.
Sources: BUILDING.md:5-11, package.json:8-22, src-tauri/tauri.conf.json:7-11
Automation Scripts
The package.json file defines the primary automation commands for the CI/CD pipeline. These scripts handle cleanup, building, and platform-specific deployments.
| Script | Action | Tool |
|---|---|---|
build | Compiles web assets into the dist folder | Vite |
clean | Removes the dist folder and server.js | Shell |
tauri:build | Generates desktop installers | Tauri CLI |
cap:sync | Syncs web assets to mobile projects | Capacitor CLI |
cap:android | Builds and opens the Android project | Capacitor/Android Studio |
cap:ios | Builds and opens the iOS project | Capacitor/Xcode |
lint | Performs static type checking | TypeScript |
test | Executes the test suite | Vitest |
Sources: package.json:8-22
Desktop Deployment Configuration
Tauri manages the desktop build process for Windows and macOS. The tauri.conf.json file specifies build commands and output targets.
Desktop Build Specifications
- Identifier:
com.agentstudio.mcpengine - Frontend Directory:
../dist - Desktop Window Dimensions: 1280x800 (minimum 800x600)
- Bundle Targets:
nsis(Windows),dmg(macOS) - Build Pre-hooks: The system runs
npm run buildbefore starting the Tauri build process.
Sources: src-tauri/tauri.conf.json:1-35
Desktop Compilation Flow
This sequence details the interaction between the CI runner, the web build tools, and the Rust compiler during a desktop release.
Sources: BUILDING.md:46-52, src-tauri/tauri.conf.json:7-11
Platform Matrix and Tooling
The application supports various hardware architectures through cross-compilation and native SDKs.
| Platform | Runner | Tooling Required |
|---|---|---|
| Windows x64 | windows-latest | Rust, Visual Studio C++ Build Tools |
| Windows ARM64 | windows-latest | Rust (aarch64-pc-windows-msvc target) |
| macOS Universal | macos-latest | Xcode, Rust (universal-apple-darwin target) |
| Android | ubuntu-latest | Android SDK, JDK 17+ |
| iOS | macos-latest | Xcode 15+, CocoaPods |
Sources: BUILDING.md:15-38, BUILDING.md:105-110
Versioning and Security Updates
The project maintains specific security support tiers for different major versions. Automated builds must align with these supported branches to receive updates.
| Version | Support Status |
|---|---|
| 5.1.x | Active Support |
| 5.0.x | End of Life |
| 4.0.x | Active Support |
| < 4.0 | End of Life |
Sources: SECURITY.md:7-12
Continuous Integration Recommendations
For automated builds, the project utilizes GitHub Actions. The following practices ensure reliable builds:
- Desktop Secrets: Set
GEMINI_API_KEYin environment variables during the build process. - Apple Certification: Store iOS certificates in GitHub Secrets for the
macos-latestrunner. - Android Signing: Use the Android SDK action on
ubuntu-latestto sign release APKs. - Targeting: Use
--target universal-apple-darwinon Mac runners to produce fat binaries for both Intel and Apple Silicon.
Sources: BUILDING.md:95-99, BUILDING.md:103-112, README.md:13
Summary
The Agent Studio CI/CD pipeline leverages a multi-tool approach to bridge the gap between web development and native distribution. By combining Vite for asset generation with Tauri and Capacitor for native wrapping, the project maintains a single codebase that deploys to four distinct operating systems. Automated workflows on GitHub Actions facilitate frequent, reliable releases across multiple hardware architectures.