Skip to content

MLE-26874 optimize kubeninjas pipelines for SBOM generation#468

Open
vitalykorolev wants to merge 2 commits into
developfrom
MLE-26874_optimize-kubeninjas-pipelines-for-SBOM-generation
Open

MLE-26874 optimize kubeninjas pipelines for SBOM generation#468
vitalykorolev wants to merge 2 commits into
developfrom
MLE-26874_optimize-kubeninjas-pipelines-for-SBOM-generation

Conversation

@vitalykorolev

Copy link
Copy Markdown
Collaborator

Description

BlackDuck scan will only be triggered from master/develop/release* branches in order to keep the number of scans for SBOM generation to a manageable level.

Checklist:

  • Owner:
  • JIRA_ID as part of branch/PR name

  • Rebase the branch with upstream

  • Squashed all commits into a single commit

  • Added Tests

  • Reviewer:
  • Reviewed Tests

  • Added to Release Wiki/Jira

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Limits when the Jenkins pipeline triggers the BlackDuck SBOM/security scan so it only runs on key branches, reducing scan volume and keeping SBOM generation manageable.

Changes:

  • Updated the BlackDuck-Scan stage gating to run only on develop, master, and release* branches via a regex branch matcher.

Comment thread Jenkinsfile
@vitalykorolev vitalykorolev changed the title Mle 26874 optimize kubeninjas pipelines for SBOM generation MLE-26874 optimize kubeninjas pipelines for SBOM generation Jul 25, 2026
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.

2 participants