ci: Sonarqube not running when only frontend changes
spbolton opened this issue · comments
Parent Issue
No response
Task
Sonarcube step in the workflow depends upon backend test steps to be able to collect coverage data from all dependencies. When there are only frontend changes we skip a lot of these steps. This is causing the sonarqube step itself to skip. we need to control the flow so the sonarqubue step still runs even when dependent steps are skipped, yet we still want to cancel the current step if the dependencies are canceled. The logic is a bit funky for this as there are specially functions for failed, success, and cancelled, but not skipped. always() can be used but it prevents cancelling
The logic to use seems to be "always() && ! canceled()", we could add && !failed() if we wanted to not run if any test steps error.
Proposed Objective
Code Maintenance
Proposed Priority
Priority 2 - Important
Acceptance Criteria
Sonarqueue runs when only frontend changes are committed.
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response