PPHA-783: favicon and manifest file (#449) #301
cicd-2-main-branch.yaml
on: push
Set CI/CD metadata
4s
Commit stage
/
Scan secrets
9s
Commit stage
/
Check file format
8s
Commit stage
/
Check Markdown format
7s
Commit stage
/
Check English usage
7s
Commit stage
/
Count lines of code
7s
Commit stage
/
Scan dependencies
44s
Test stage
/
Test coverage
6s
Test stage
/
Perform static analysis
5s
Matrix: Deploy stage / Deploy
Acceptance stage
/
Contract test
6s
Acceptance stage
/
Security test
6s
Acceptance stage
/
UI test
4m 32s
Acceptance stage
/
UI performance test
3s
Acceptance stage
/
Integration test
3s
Acceptance stage
/
Accessibility test
5s
Acceptance stage
/
Load test
4s
Acceptance stage
/
Environment tear down
4s
Annotations
4 warnings
|
Commit stage / Count lines of code
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Commit stage / Scan dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build stage / Build
Please check that the "artifact-metadata:write" permission has been included
|
|
Build stage / Build
Failed to create storage record: Error: Failed to persist storage record: no artifacts found - https://docs.github.com/rest/orgs/artifact-metadata#create-artifact-metadata-storage-record
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
NHSDigital~lung_cancer_screening~OPPXQB.dockerbuild
|
32.7 KB |
sha256:2d5ba8f4ceb6a6bc811781f652a53a29312f2e5b386060e543926fa0849c1071
|
|
|
lines-of-code-report.json.zip
|
882 Bytes |
sha256:77f70012b6a0f623d289dcf9b645cc9a14f249bc91d6d1e2de3c8c0e9e5a186b
|
|
|
sbom-repository-report.json.zip
|
71.2 KB |
sha256:7329047d5ed7f4cbb90cb6a6c5db2775e816b31f6d91ddf917acacf0c22b48d5
|
|
|
vulnerabilities-repository-report.json.zip
|
2.4 KB |
sha256:8f5d21093c246afb3c1f3d6adee634239792f4a1eb4c73ae3f7e27649cc72b96
|
|