Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(importCDX): Add functionality to configure release creation when importing SBOM to an existing project #2458

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sameed20
Copy link
Contributor

This PR introduces the feature that allows users to configure release creation when importing CycloneDX SBOM to an existing project.

closes: #2435

@sameed20 sameed20 force-pushed the feat/enable-users-to-configure-release-creation-on-importing-SBOM-on-an-existing-project-2435 branch from 72f9853 to 0c94fe8 Compare May 15, 2024 16:38
@akshitjoshii
Copy link
Contributor

Testing this PR.

@afsahsyeda afsahsyeda added needs code review needs general test This is general testing, meaning that there is no org specific issue to check for labels May 20, 2024
@akshitjoshii
Copy link
Contributor

@sameed20 The REST API docs have not been updated. Pls update the docs for this endpoint as well

@sameed20 sameed20 force-pushed the feat/enable-users-to-configure-release-creation-on-importing-SBOM-on-an-existing-project-2435 branch from 0c94fe8 to 6d622d7 Compare May 21, 2024 05:39
@akshitjoshii
Copy link
Contributor

akshitjoshii commented May 22, 2024

@sameed20 Feature is working as expected if the component has a VCS field in the SBOM for both orphan and non-orphan pkgs. But if an orphan pkg is present in the project and the SBOM also has different version of the orphan pkg then the it is simply adding the orphan pkgs and never replacing it. Same behaviour is seen when imported from UI or rest.

@sameed20 sameed20 force-pushed the feat/enable-users-to-configure-release-creation-on-importing-SBOM-on-an-existing-project-2435 branch from 6d622d7 to 2fa92ee Compare June 2, 2024 13:00
@sameed20 sameed20 force-pushed the feat/enable-users-to-configure-release-creation-on-importing-SBOM-on-an-existing-project-2435 branch 2 times, most recently from 6b2e89f to c9aa23f Compare June 5, 2024 09:42
@sameed20 sameed20 force-pushed the feat/enable-users-to-configure-release-creation-on-importing-SBOM-on-an-existing-project-2435 branch from c9aa23f to c5311b1 Compare June 25, 2024 17:04
@sameed20 sameed20 force-pushed the feat/enable-users-to-configure-release-creation-on-importing-SBOM-on-an-existing-project-2435 branch from c5311b1 to 9f45c16 Compare June 27, 2024 06:05
… importing SBOM to an existing project

Signed-off-by: sameed.ahmad <[email protected]>
@sameed20 sameed20 force-pushed the feat/enable-users-to-configure-release-creation-on-importing-SBOM-on-an-existing-project-2435 branch from 9f45c16 to b2664f4 Compare September 18, 2024 06:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs code review needs general test This is general testing, meaning that there is no org specific issue to check for
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable users to configure release creation on importing SBOM on an existing project
3 participants