Skip to content

feat(ci): advanced triggers for ci-core#21685

Open
erikburt wants to merge 6 commits intodevelopfrom
feat/ci-core-advanced-triggers
Open

feat(ci): advanced triggers for ci-core#21685
erikburt wants to merge 6 commits intodevelopfrom
feat/ci-core-advanced-triggers

Conversation

@erikburt
Copy link
Copy Markdown
Collaborator

@erikburt erikburt commented Mar 24, 2026

This adds a new step advanced-triggers which in the future will be used to gate jobs more effectively. This is on purpose for a "roll-out" phase where we will continue to rely on the old-logic, but can cross-reference what the new logic would've done, and if it was correct.

Changes

  • Adds configuration for advanced-triggers
    • Translates the existing path filters, and add more granular path filtering/exclusions to avoid unnecessary runs

Notes

Related to #21659, #21686.

Testing

Tested these triggers during development:


DX-3534

@erikburt erikburt self-assigned this Mar 24, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 24, 2026

✅ No conflicts with other open PRs targeting develop

@erikburt erikburt marked this pull request as ready for review March 24, 2026 22:05
@erikburt erikburt requested review from a team as code owners March 24, 2026 22:05
Copilot AI review requested due to automatic review settings March 24, 2026 22:05
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Risk Rating: HIGH — Changes affect CI gating/trigger logic for ci-core, with potential for missed test execution or unexpected resource usage.

This PR migrates ci-core change detection from dorny/paths-filter to the shared advanced-triggers action, aiming to reduce unnecessary workflow runs via more granular file-set based triggers.

Changes:

  • Replace dorny/paths-filter-based outputs with advanced-triggers outputs (core-tests, core-fuzz-tests, core-race-tests, core-integration-tests, deployment-tests).
  • Define reusable file-sets and per-job trigger rules using inclusion/exclusion sets and explicit paths.
  • Update downstream should-run selectors to use the new trigger outputs.

@trunk-io
Copy link
Copy Markdown

trunk-io bot commented Mar 24, 2026

Static BadgeStatic BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

@erikburt erikburt force-pushed the feat/ci-core-advanced-triggers branch from 20e9540 to fcb5b10 Compare March 24, 2026 22:38
@erikburt erikburt requested a review from kalverra April 1, 2026 16:54
@cl-sonarqube-production
Copy link
Copy Markdown

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

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.

3 participants