GitLab

Pipeline Status: FAILURE
FAILURE Stage: Create CSV Scan Output Branch: 5.3.1

graph LR
  0([setup]):::INTERNAL_SUCCESS --> 1([Import Artifacts]):::SUCCESS --> 2((/)):::INTERNAL_SUCCESS --> 3([Stage Artifacts]):::SUCCESS --> 4((/)):::INTERNAL_SUCCESS --> 5([Build]):::SUCCESS --> 6([Publish, Scan & Report]):::INTERNAL_FAILURE

classDef SUCCESS font-size:10px
classDef FAILURE fill:#f00, stroke:#700, font-size:10px
classDef SKIPPED font-size:10px
classDef ABORTED fill:#889, font-size:10px
classDef INTERNAL_SUCCESS font-size:10px, stroke-dasharray: 2, 1
classDef INTERNAL_FAILURE fill:#f00, stroke:#700, font-size:10px, stroke-dasharray: 2, 1
classDef INTERNAL_SKIPPED font-size:10px, stroke-dasharray: 2, 1
classDef INTERNAL_ABORTED fill:#889, font-size:10px, stroke-dasharray: 2, 1

@balan-karpagam your code passed the build phase but there was a pipeline failure. I guess you would reach out to someone on the Iron Bank team to investigate.

@Smith why is this build failing?

https://jenkins.apps.cluster.dsop.io/job/dsop/job/solutions-delivery-platform/job/dependency-check/job/dependency-check/job/5.3.1/12/console

@gfulton it looks like the CSV generator is croaking processing the Twistlock report.

I'm going to investigate this further - this is the first time I have seen this issue and those CSV scan scripts have not changed recently.

	@Library('DCCSCR@master') _		@Library('DCCSCR@23-contributor-status-report') _
	dccscrPipeline(version: "5.3.1")		dccscrPipeline(version: "5.3.1")

Apply suggestion to Jenkinsfile