Skip to content

ci: pr-cve-check only scan changed recipes#15499

Merged
rpcme merged 1 commit intoaws4embeddedlinux:master-nextfrom
rpcme:fix/pr-cve-check-changed-only
Apr 21, 2026
Merged

ci: pr-cve-check only scan changed recipes#15499
rpcme merged 1 commit intoaws4embeddedlinux:master-nextfrom
rpcme:fix/pr-cve-check-changed-only

Conversation

@rpcme
Copy link
Copy Markdown
Member

@rpcme rpcme commented Apr 20, 2026

Problem

The pr-cve-check workflow runs CVE checks against every .bb recipe in the layer on every PR, regardless of what changed. This causes very long run times (50+ minutes and counting).

Fix

Add a changed job (mirroring the build-test-recipe pattern) that:

  1. Detects which .bb/.inc files were modified in the PR
  2. Extracts recipe names from the changed files
  3. Only runs CVE checks on those specific recipes
  4. Skips the heavy CVE check job entirely if no recipe files changed

Testing

The diff detection logic mirrors the proven pattern from build-test-recipe.yml.

The pr-cve-check workflow was running CVE checks against every .bb
recipe in the layer on every PR, causing very long run times.

Add a 'changed' job (mirroring build-test-recipe pattern) that detects
which recipes were modified in the PR, then only CVE-check those.
Skip the CVE check entirely if no recipe files changed.
@rpcme rpcme requested a review from a team as a code owner April 20, 2026 19:16
@rpcme rpcme enabled auto-merge April 20, 2026 22:26
@rpcme rpcme disabled auto-merge April 20, 2026 22:29
@rpcme rpcme enabled auto-merge April 20, 2026 22:29
@rpcme rpcme self-assigned this Apr 20, 2026
@rpcme rpcme added this pull request to the merge queue Apr 20, 2026
Merged via the queue into aws4embeddedlinux:master-next with commit 62d4540 Apr 21, 2026
8 of 9 checks passed
@rpcme rpcme deleted the fix/pr-cve-check-changed-only branch April 21, 2026 02:51
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