Skip to content
CI/CD pull request

Attempting to fix Scan Secrets error by renaming key to key_name #1358

Sign in to view logs

Attempting to fix Scan Secrets error by renaming key to key_name

Attempting to fix Scan Secrets error by renaming key to key_name #1358

Triggered via push September 11, 2025 14:29
@adrianoaru-nhsadrianoaru-nhs
pushed 203cd88
feature/BCSS-21494-subject-criteria-ui-application
Status Failure
Total duration 1m 6s
Artifacts 3

cicd-1-pull-request.yaml

on: push
Set CI/CD metadata
5s
Set CI/CD metadata
Commit stage  /  Scan secrets
15s
Commit stage / Scan secrets
Commit stage  /  Check file format
4s
Commit stage / Check file format
Commit stage  /  Check Markdown format
8s
Commit stage / Check Markdown format
Commit stage  /  Check English usage
9s
Commit stage / Check English usage
Commit stage  /  Count lines of code
5s
Commit stage / Count lines of code
Commit stage  /  Scan dependencies
49s
Commit stage / Scan dependencies
Test stage  /  Run Util Tests
Test stage / Run Util Tests
Fit to window
Zoom out
Zoom in

Annotations

1 error
Commit stage / Scan secrets
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size Digest
lines-of-code-report.json.zip Expired
835 Bytes
sha256:40b6a943839983176f6d83fb995e14be46900cafe0b25f3deb2f566939d1e6d2
sbom-repository-report.json.zip Expired
36.9 KB
sha256:24cffb00676680d811e925e42fb4583d9c45f1b2d3948f785e1c333a9fd5af6d
vulnerabilities-repository-report.json.zip Expired
1.38 KB
sha256:14552f49d6788e2d2bec7d7b3a33e275fbf819e4f2dceb39bf91b74765874ddd