Skip to content

Split build and release workflows for gui and cli#816

Closed
eliykat wants to merge 1 commit intomainfrom
split-build-release-workflows
Closed

Split build and release workflows for gui and cli#816
eliykat wants to merge 1 commit intomainfrom
split-build-release-workflows

Conversation

@eliykat
Copy link
Member

@eliykat eliykat commented Jul 8, 2025

🎟️ Tracking

N/A but I'll create a ticket if we accept this proposal

📔 Objective

Split the build and release workflows by client, so that we can build and release CLI and GUI clients separately.

My primary reason here is maintainability - the build workflow is currently 651 LOC with 6 different build jobs for all the combinations of platform x app, which is hard to keep track of in a yaml file. This change also matches how our monorepo workflows are structured; avoids mixing app-specific setup steps; and would allow for separate releases if required (e.g. if we had a CLI/GUI specific bug we wanted to fix).

The downside is some duplication in setup and completion jobs in each workflow, but I think this is minimal. There may also be some process overhead when we do a release which we can discuss as a team.

📸 Screenshots

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 8, 2025

@codecov
Copy link

codecov bot commented Jul 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 7.71%. Comparing base (284206b) to head (e2bf699).

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@          Coverage Diff          @@
##            main    #816   +/-   ##
=====================================
  Coverage   7.71%   7.71%           
=====================================
  Files         68      68           
  Lines       2760    2760           
  Branches     477     477           
=====================================
  Hits         213     213           
  Misses      2532    2532           
  Partials      15      15           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2025

Logo
Checkmarx One – Scan Summary & Detailsbe630117-a7d6-4a71-ba0a-a3d98fb4244c

Great job, no security vulnerabilities found in this Pull Request

@eliykat
Copy link
Member Author

eliykat commented Jul 8, 2025

This would have some downstream consequences we don't want to deal with right now - we have more important things to address in this repo so we may come back to it later.

@eliykat eliykat closed this Jul 8, 2025
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