Skip to content

ci: parallel arm64 builds on develop#176

Merged
nitrobass24 merged 1 commit intodevelopfrom
ci/parallel-arm-develop
Mar 6, 2026
Merged

ci: parallel arm64 builds on develop#176
nitrobass24 merged 1 commit intodevelopfrom
ci/parallel-arm-develop

Conversation

@nitrobass24
Copy link
Owner

@nitrobass24 nitrobass24 commented Mar 6, 2026

Summary

  • Extract Angular build into its own job so it runs in parallel with unit tests and amd64 builds
  • Enable arm64 builds on develop pushes (previously only on release tags)
  • Unify publish-develop into the main publish job with branch-aware tagging (develop vs semver)

New flow (develop push)

unit-test ──────────────────────────────────┐
angular-build ──→ build-arm64 ──────────────┼──→ publish (multi-arch: develop/develop-alpine)
build (amd64) ──────────────────────────────┘

All three top-level jobs start immediately in parallel. arm64 only waits for the Angular build artifact (~30s), not the full test suite.

Test plan

  • Verify CI passes on this PR (unit-test + build only, no publish)
  • After merge to develop, verify all jobs run including arm64 build and multi-arch publish
  • Verify develop and develop-alpine tags are multi-arch (amd64 + arm64)

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Optimized continuous integration pipeline with consolidated publishing conditions and streamlined build job dependencies
    • Enhanced automated build and release workflow to support multiple deployment scenarios

- Extract Angular build into its own job (runs in parallel with tests + amd64 build)
- Enable arm64 builds on develop pushes (not just release tags)
- Unify publish-develop into the main publish job with branch-aware tagging
- All three top-level jobs (unit-test, angular-build, build) start immediately in parallel

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai
Copy link

coderabbitai bot commented Mar 6, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5064d249-7aa8-4637-8005-66cbe26c6b5a

📥 Commits

Reviewing files that changed from the base of the PR and between d067ffa and aa29fe5.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml

📝 Walkthrough

Walkthrough

The CI workflow consolidates publishing conditions to trigger on both version tags and develop-branch pushes. The changes reorganize job dependencies by introducing an angular-build job, making build-arm64 depend on it, and refactoring metadata extraction steps to distinguish between release and develop contexts. The separate publish-develop workflow section is removed in favor of expanded publish job conditions.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow
.github/workflows/ci.yml
Consolidated SHOULD_PUBLISH condition to trigger on version tags or develop pushes; added angular-build job with conditional gating; updated build-arm64 job dependencies; refactored metadata extraction steps to separate release (debian-release, alpine-release) and develop (debian-develop, alpine-develop) contexts; expanded publish job conditions to handle both release and develop triggers.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

Poem

🐰 Hops of joy for workflows refined,
Publishing conditions now combined!
Release and develop, side by side,
Job dependencies set with pride—
The CI pipeline flows with grace!

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ci/parallel-arm-develop

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@nitrobass24 nitrobass24 merged commit 926c64f into develop Mar 6, 2026
8 of 9 checks passed
@nitrobass24 nitrobass24 deleted the ci/parallel-arm-develop branch March 6, 2026 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant