gronod/MacMonitor
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Gitea Actions CI/CD Pipeline for Intel macOS Builds #25

New Issue
Closed
opened 2026-09-08 10:29:52 +01:00 by gronod · 2 comments
gronod commented 2026-09-08 10:29:52 +01:00
Owner
Copy Link
Copy Source

Purpose

Automate the continuous integration and delivery lifecycle for MacMonitor using Gitea Actions runners, ensuring every commit and pull request compiles cleanly against macOS 14+ SDK for Intel x86_64 and passes automated test suites.

Priority

High (Guarantees build integrity, Intel x86_64 architecture verification, and regression prevention)

Dependencies

  • Depends on #1 (Core Application Architecture & Objective-C/SwiftUI Bridging Foundation)

Scope

  • Configure Gitea Actions workflow .gitea/workflows/build.yml.
  • Target self-hosted or managed macOS Intel runners.
  • Automate:
    • Xcode workspace / project compilation targeting x86_64
    • Execution of XCTest test suites (mocking hardware/SMC layers where appropriate)
    • SwiftLint / code style analysis
    • Archive generation (.app / .zip artifact upload) on tagged releases
  • Report build status back to Gitea commit statuses and pull requests.

Implementation Suggestions

  • Define workflow YAML with runs-on: [macos, intel] or matching Gitea runner tags.
  • Execute builds via command line:
    xcodebuild build test -scheme MacMonitor -destination 'generic/platform=macOS,arch=x86_64' CODE_SIGNING_ALLOWED=NO
  • Use Actions artifact upload steps to attach zipped .app bundles to Gitea release builds.
### Purpose Automate the continuous integration and delivery lifecycle for MacMonitor using Gitea Actions runners, ensuring every commit and pull request compiles cleanly against macOS 14+ SDK for Intel x86_64 and passes automated test suites. ### Priority **High** (Guarantees build integrity, Intel x86_64 architecture verification, and regression prevention) ### Dependencies - Depends on #1 (Core Application Architecture & Objective-C/SwiftUI Bridging Foundation) ### Scope - Configure Gitea Actions workflow `.gitea/workflows/build.yml`. - Target self-hosted or managed macOS Intel runners. - Automate: - Xcode workspace / project compilation targeting `x86_64` - Execution of XCTest test suites (mocking hardware/SMC layers where appropriate) - SwiftLint / code style analysis - Archive generation (`.app` / `.zip` artifact upload) on tagged releases - Report build status back to Gitea commit statuses and pull requests. ### Implementation Suggestions - Define workflow YAML with `runs-on: [macos, intel]` or matching Gitea runner tags. - Execute builds via command line: `xcodebuild build test -scheme MacMonitor -destination 'generic/platform=macOS,arch=x86_64' CODE_SIGNING_ALLOWED=NO` - Use Actions artifact upload steps to attach zipped `.app` bundles to Gitea release builds.
gronod added the Kind/Feature
Priority
High
2
Project/AntigravityFeature/DevOps labels 2026-09-08 10:29:52 +01:00
gronod commented 2026-09-08 10:41:26 +01:00
Author
Owner
Copy Link
Copy Source

Technical Implementation Plan & Code Solution

1. Gitea Actions Architecture

The continuous integration pipeline automates building and verifying MacMonitor on self-hosted or managed macOS Intel runners.

flowchart TD
    TRIGGER["Git Push / Pull Request Event"] --> RUNNER["Gitea Actions Runner<br/>(macOS Intel x86_64)"]
    RUNNER --> STEP1["1. Verify Environment<br/>(Xcode 15+ / macOS 14 SDK)"]
    STEP1 --> STEP2["2. xcodebuild Compilation<br/>(generic/platform=macOS,arch=x86_64)"]
    STEP2 --> STEP3["3. Run XCTest Suite<br/>(Mocked AppleSMC & Mach providers)"]
    STEP3 --> STEP4["4. Archive & Package<br/>(Zip MacMonitor.app)"]
    STEP4 --> STEP5["5. Upload Build Artifact<br/>(MacMonitor-intel-x86_64.zip)"]

2. Workflow Specification (.gitea/workflows/build.yml)

name: MacMonitor Build & Test

on:
  push:
    branches:
      - main
      - develop
    tags:
      - 'v*'
  pull_request:
    branches:
      - main
      - develop

jobs:
  build-and-test:
    name: Build & Verify (Intel x86_64)
    runs-on: [macos, intel]

    steps:
      - name: Checkout Code
        uses: actions/checkout@v4

      - name: Verify Environment & Tools
        run: |
          sw_vers
          uname -m
          xcodebuild -version

      - name: Build MacMonitor (x86_64)
        run: |
          xcodebuild build \
            -scheme MacMonitor \
            -destination 'generic/platform=macOS,arch=x86_64' \
            -configuration Release \
            CODE_SIGNING_ALLOWED=NO \
            CODE_SIGNING_REQUIRED=NO

      - name: Run Test Suite
        run: |
          xcodebuild test \
            -scheme MacMonitor \
            -destination 'platform=macOS,arch=x86_64' \
            CODE_SIGNING_ALLOWED=NO

      - name: Archive Application Artifact
        if: startsWith(github.ref, 'refs/tags/v')
        run: |
          ditto -c -k --sequesterRsrc --keepParent \
            build/Release/MacMonitor.app \
            MacMonitor-intel-x86_64.zip

      - name: Upload Artifact
        if: startsWith(github.ref, 'refs/tags/v')
        uses: actions/upload-artifact@v4
        with:
          name: MacMonitor-Intel-Release
          path: MacMonitor-intel-x86_64.zip

3. Verification & Mocking in Unit Tests

Unit tests in CI test provider decoding logic against synthetic SMC and Mach structures (e.g. mock sp78 bytes, simulated vm_statistics64) ensuring tests execute reliably on runners without requiring physical AppleSMC hardware.

## Technical Implementation Plan & Code Solution ### 1. Gitea Actions Architecture The continuous integration pipeline automates building and verifying MacMonitor on self-hosted or managed macOS Intel runners. ```mermaid flowchart TD TRIGGER["Git Push / Pull Request Event"] --> RUNNER["Gitea Actions Runner<br/>(macOS Intel x86_64)"] RUNNER --> STEP1["1. Verify Environment<br/>(Xcode 15+ / macOS 14 SDK)"] STEP1 --> STEP2["2. xcodebuild Compilation<br/>(generic/platform=macOS,arch=x86_64)"] STEP2 --> STEP3["3. Run XCTest Suite<br/>(Mocked AppleSMC & Mach providers)"] STEP3 --> STEP4["4. Archive & Package<br/>(Zip MacMonitor.app)"] STEP4 --> STEP5["5. Upload Build Artifact<br/>(MacMonitor-intel-x86_64.zip)"] ``` --- ### 2. Workflow Specification (`.gitea/workflows/build.yml`) ```yaml name: MacMonitor Build & Test on: push: branches: - main - develop tags: - 'v*' pull_request: branches: - main - develop jobs: build-and-test: name: Build & Verify (Intel x86_64) runs-on: [macos, intel] steps: - name: Checkout Code uses: actions/checkout@v4 - name: Verify Environment & Tools run: | sw_vers uname -m xcodebuild -version - name: Build MacMonitor (x86_64) run: | xcodebuild build \ -scheme MacMonitor \ -destination 'generic/platform=macOS,arch=x86_64' \ -configuration Release \ CODE_SIGNING_ALLOWED=NO \ CODE_SIGNING_REQUIRED=NO - name: Run Test Suite run: | xcodebuild test \ -scheme MacMonitor \ -destination 'platform=macOS,arch=x86_64' \ CODE_SIGNING_ALLOWED=NO - name: Archive Application Artifact if: startsWith(github.ref, 'refs/tags/v') run: | ditto -c -k --sequesterRsrc --keepParent \ build/Release/MacMonitor.app \ MacMonitor-intel-x86_64.zip - name: Upload Artifact if: startsWith(github.ref, 'refs/tags/v') uses: actions/upload-artifact@v4 with: name: MacMonitor-Intel-Release path: MacMonitor-intel-x86_64.zip ``` --- ### 3. Verification & Mocking in Unit Tests Unit tests in CI test provider decoding logic against synthetic SMC and Mach structures (e.g. mock `sp78` bytes, simulated `vm_statistics64`) ensuring tests execute reliably on runners without requiring physical AppleSMC hardware.
gronod added this to the M1: Architecture Foundation & Hardware Abstraction milestone 2026-09-08 10:41:56 +01:00
gronod commented 2026-09-08 12:13:55 +01:00
Author
Owner
Copy Link
Copy Source

Implementation Completed (Milestone 1)

The Gitea Actions CI/CD Pipeline for Intel macOS Builds has been implemented in commit ad2695a on branch feat/25-gitea-ci and merged into milestone/m1-foundation (commit f034771).

Delivered Components:

  • Workflow Specification (.gitea/workflows/build.yml): Targeting [macos, intel] runners.
  • Triggers: Configured for push and pull_request events across main, develop, milestone/**, and feat/** branches.
  • Pipeline Steps:
    1. Environment and toolchain inspection (uname -m, sw_vers, xcodebuild -version, xcrun --show-sdk-path).
    2. Deterministic project generation via xcodegen generate with tracked .xcodeproj fallback.
    3. SwiftLint lint validation.
    4. Application compilation targeting generic/platform=macOS,arch=x86_64 with CODE_SIGNING_ALLOWED=NO.
    5. XCTest execution across all unit test suites piped through xcbeautify.
### Implementation Completed (Milestone 1) The Gitea Actions CI/CD Pipeline for Intel macOS Builds has been implemented in commit `ad2695a` on branch `feat/25-gitea-ci` and merged into `milestone/m1-foundation` (commit `f034771`). **Delivered Components:** - **Workflow Specification (`.gitea/workflows/build.yml`)**: Targeting `[macos, intel]` runners. - **Triggers**: Configured for `push` and `pull_request` events across `main`, `develop`, `milestone/**`, and `feat/**` branches. - **Pipeline Steps**: 1. Environment and toolchain inspection (`uname -m`, `sw_vers`, `xcodebuild -version`, `xcrun --show-sdk-path`). 2. Deterministic project generation via `xcodegen generate` with tracked `.xcodeproj` fallback. 3. SwiftLint lint validation. 4. Application compilation targeting `generic/platform=macOS,arch=x86_64` with `CODE_SIGNING_ALLOWED=NO`. 5. XCTest execution across all unit test suites piped through `xcbeautify`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Bug/Architecture
Architecture & Foundation Defect
 Bug/Backend
Backend, service, or low-level logic defect
 Bug/DevOps
CI/CD, build system, and automation defect
 Bug/Documentation
Documentation inaccuracy or fix
 Bug/Performance
Performance regression or degradation defect
 Bug/Security
Security vulnerability or flaw
 Bug/Testing
Test failure or testing defect
 Bug/UI
User interface and presentation defect
 Compat/Breaking
Breaking change that won't be backward compatible
 Feature/Architecture
Architecture & Foundation Feature
 Feature/Backend
Backend, service, or low-level logic feature
 Feature/DevOps
CI/CD, build system, and automation feature
 Feature/Documentation
Documentation additions and features
 Feature/Performance
Performance optimization feature
 Feature/Security
Security capability or hardening feature
 Feature/Testing
Test suite, mock, or testing harness feature
 Feature/UI
User interface and presentation feature
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Project/Antigravity
Part of the Antigravity Project specification
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No labels Feature/DevOps Kind/Feature
Priority
High
2
 Project/Antigravity
Milestone
No items
No Milestone M1: Architecture Foundation & Hardware Abstraction
Projects
Clear projects
No projects
Assignees
Clear assignees
gronod
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#1 Core Application Architecture & Objective-C/SwiftUI Bridging Foundation
gronod/MacMonitor
Reference: gronod/MacMonitor#25