Re: [isar-cip-core v2 0/3] Generate CVE-reports only with manual trigger

From: Jan Kiszka <jan.kiszka@siemens.com>
To: Sai.Sathujoda@toshiba-tsip.com, cip-dev@lists.cip-project.org
Cc: dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: Re: [isar-cip-core v2 0/3] Generate CVE-reports only with manual trigger
Date: Thu, 18 Jan 2024 19:20:51 +0100	[thread overview]
Message-ID: <8f51796d-1f88-4572-bbb6-c31efffa3003@siemens.com> (raw)
In-Reply-To: <20240118175942.1052089-1-Sai.Sathujoda@toshiba-tsip.com>

On 18.01.24 18:59, Sai.Sathujoda@toshiba-tsip.com wrote:
> From: Sai Sathujoda <Sai.Sathujoda@toshiba-tsip.com>
> 
> This series of patches enables generation of CVE-reports from a latest copy of
> dpkg-status files stored in CIP project's s3 bucket only when they are manually
> started in the pipeline.
> 
> The cve-checker.py script in debian-cve-checker repository [1] is used to generate
> the CVE-reports from the dpkg-status of repsective targets.
> 
> [1] https://gitlab.com/cip-playground/debian-cve-checker
> 
> Sai Sathujoda (3):
>   scripts/run-cve-checks.sh: Add script to generate CVE report
>   scripts/deploy-cip-core.sh: Upload dpkg-status files to aws s3 bucket
>   .gitlab-ci.yml: Run cve-checks job only when it is manually triggered
>     in the pipeline
> 
>  .gitlab-ci.yml             | 14 +++++++++++++
>  scripts/deploy-cip-core.sh | 12 ++++++++++++
>  scripts/run-cve-checks.sh  | 40 ++++++++++++++++++++++++++++++++++++++
>  3 files changed, 66 insertions(+)
>  create mode 100755 scripts/run-cve-checks.sh
> 

Thanks, applied - with warning fixes. Please check next branch.

Jan

-- 
Siemens AG, Technology
Linux Expert Center