From: Simon Falsig <sfalsig@verity.net>
To: Bruno Thomsen <bruno.thomsen@gmail.com>,
"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] RFC: sbom_report: Add support
Date: Fri, 3 Nov 2023 07:34:19 +0000 [thread overview]
Message-ID: <GV0P278MB0784B052FF6C85E13FD932C0CBA5A@GV0P278MB0784.CHEP278.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAH+2xPC-X4Ky9ewVZL+1OaCpnW7qqGYmBBXVWHZbmbjWXvN+cA@mail.gmail.com>
> -----Original Message-----
> From: Bruno Thomsen <bruno.thomsen@gmail.com>
> Sent: Saturday, October 21, 2023 15:52
> Subject: Re: [ptxdist] [PATCH] RFC: sbom_report: Add support
>
> Den man. 18. sep. 2023 kl. 16.34 skrev Simon Falsig <sfalsig@verity.net>:
> >
> > From: Simon Falsig <sfalsig@verity.ch>
> >
> > This provides support for building SBOMs in CycloneDX format.
> >
> > A target is added alongside the other reports, that (based on the
> > fast-bsp-report) extracts name, version, cpe and license of each
> > target package, and puts these into a final sbom-report in
> > CycloneDX/JSON format.
> >
> > This requires a working Python3 setup with the cyclonedx-bom package
> > installed.
>
> Hi Simon,
>
> I have tested this together with GitLab Dependency Scanning in Ultimate
> SaaS, and it seems to be working well.
>
> Tested-by: Bruno Thomsen <bruno.thomsen@gmail.com>
>
> .gitlab-ci.yml example snippet:
>
> -------------8<-------------
>
> ptxdist sbom:
> stage: build
> script:
> - cd ptxdist
> - ./p sbom-report
> artifacts:
> reports:
> dependency_scanning: <platform-dir>/release/sbom-report.json
>
> -------------8<-------------
>
> Thanks for working on this.
>
> /Bruno
>
Thanks, Bruno!
I've sadly not had time to work more on this lately, but am hoping to pick it up again later in November.
A bit stuck on how to properly provide / ensure that the needed Python cyclonedx libraries are available on the system. If anyone has any suggestions, I'd be happy to hear them :)
Best regards,
Simon
next prev parent reply other threads:[~2023-11-03 7:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 16:05 [ptxdist] [PATCH 1/3] RFC: ptxd_make_world: Extract CPE for packages Simon Falsig
2023-09-13 16:05 ` [ptxdist] [PATCH 2/3] RFC: Add CPE for a few packages Simon Falsig
2023-09-15 10:15 ` [ptxdist] [PATCH] " Simon Falsig
2023-09-13 16:05 ` [ptxdist] [PATCH 3/3] RFC: sbom_report: Add support Simon Falsig
2023-09-18 14:33 ` [ptxdist] [PATCH] " Simon Falsig
2023-10-21 13:52 ` Bruno Thomsen
2023-11-03 7:34 ` Simon Falsig [this message]
2023-09-13 21:16 ` [ptxdist] [PATCH 1/3] RFC: ptxd_make_world: Extract CPE for packages Christian Melki
2023-09-14 6:46 ` Simon Falsig
2023-09-15 10:14 ` [ptxdist] [PATCH] " Simon Falsig
2023-09-15 10:39 ` Michael Olbrich
2023-09-18 14:29 ` Simon Falsig
2023-09-18 14:37 ` Simon Falsig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=GV0P278MB0784B052FF6C85E13FD932C0CBA5A@GV0P278MB0784.CHEP278.PROD.OUTLOOK.COM \
--to=sfalsig@verity.net \
--cc=bruno.thomsen@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox