feat(ci): advanced triggers for ci-core

[erikburt]

Changes

• Switch from dorny/paths-filter to new action advanced-triggers
• Translate the existing path filters, and add more granular path filtering/exclusions to avoid unnecessary runs

Notes

Related to #21659, #21686.

Want some eyes on the actual file sets and triggers:

chainlink/.github/workflows/ci-core.yml

Lines 40 to 97 in 20e9540

	- name: Advanced Triggers
	id: triggers
	uses: smartcontractkit/.github/actions/advanced-triggers@advanced-triggers/v1
	with:
	file-sets: |
	go-files:
	- "**/*.go"
	- "**/go.mod"
	- "**/go.sum"
	core-files:
	- "core/**"
	all-test-files:
	- "**/testdata/**"
	- "**/*_test.go"
	core-test-files:
	- "testdata/**"
	- "core/**/testdata/**"
	- "core/**_test.go"
	e2e-tests-files:
	- "system-tests/**"
	- "integration-tests/**"
	workflow-files:
	- ".github/workflows/ci-core.yml"
	- ".github/actions/**/*.y*ml"
	deployment-files:
	- "deployment/**"
	# Note:
	# - pull_request, merge_group, and push events will resolve to true if any changed files match the path/glob patterns
	# - exclusion-sets/negations are applied first, and therefore filter all changed files before inclusion sets are applied
	# - by default these will resolve to true for schedule, and workflow_dispatch events
	triggers: |
	core-tests:
	exclusion-sets: [ e2e-tests-files, deployment-files ]
	inclusion-sets: [ go-files, core-files, all-test-files, workflow-files ]
	paths:
	- "tools/bin/go_core_tests"
	core-fuzz-tests:
	exclusion-sets: [ e2e-tests-files, deployment-files ]
	inclusion-sets: [ go-files, core-files, all-test-files, workflow-files ]
	paths:
	- "!**/testdata/**"
	- "**/fuzz/**"
	- "tools/bin/go_core_fuzz"
	core-race-tests:
	exclusion-sets: [ e2e-tests-files, deployment-files ]
	inclusion-sets: [ go-files, core-files, all-test-files, workflow-files ]
	paths:
	- "tools/bin/go_core_race_tests"
	core-integration-tests:
	exclusion-sets: [ e2e-tests-files, deployment-files ]
	inclusion-sets: [ go-files, core-files, all-test-files, workflow-files ]
	paths:
	- "tools/bin/go_core_tests_integration"
	deployment-tests:
	exclusion-sets: [ e2e-tests-files, core-test-files ]
	inclusion-sets: [ go-files, core-files, deployment-files, workflow-files ]
	paths:
	- "tools/bin/go_core_ccip_deployment_tests"

• I believe this will be good enough, as most files are included unless they are explicitly excluded.
• But can we be more restrictive?

Given how this is already rather verbose and repetitive, I'm considering moving the input to this action, into a file like .github/advanced-triggers.yml? 🤔 Would need to add support for that in the action though, and then likely some validation of the file itself.

Testing

Tested these triggers during development:

• feat: advanced triggers .github#1473
• test: advanced trigger filters #21627

This PR - will run all tests as the workflow was modified

• https://github.com/smartcontractkit/chainlink/actions/runs/23514255349/job/68442708456?pr=21685#step:3:213

---

DX-3534

[github-actions]

✅ No conflicts with other open PRs targeting develop

[Copilot]

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]

     

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

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