Skip to content

Add index.html for redirecting to DevSecOps documentation #111

Add index.html for redirecting to DevSecOps documentation

Add index.html for redirecting to DevSecOps documentation #111

Triggered via push April 2, 2026 00:12
Status Success
Total duration 2m 45s
Artifacts 3

cicd.yml

on: push
Build and Publish Container Image  /  set-version
8s
Build and Publish Container Image / set-version
Deploy Azure Infrastructure
1m 4s
Deploy Azure Infrastructure
Build and Publish Container Image  /  ...  /  scan-image
1m 23s
Build and Publish Container Image / scan-image / scan-image
Build and Deploy to Azure Web App
1m 35s
Build and Deploy to Azure Web App
Build and Publish Container Image  /  ...  /  publish-image
1m 5s
Build and Publish Container Image / publish-image / publish-image
Fit to window
Zoom out
Zoom in

Annotations

14 warnings and 3 notices
Build and Publish Container Image / scan-image / scan-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: anchore/scan-action@7037fa011853d5a11690026fb85feee79f4c946c, docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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 and Publish Container Image / scan-image / scan-image
Failed minimum severity level. Found vulnerabilities with level 'medium' or higher
Build and Deploy to Azure Web App
Error: Failed to update deployment history. util.isNumber is not a function
Build and Deploy to Azure Web App
Converting null literal or possible null value to non-nullable type.
Build and Deploy to Azure Web App
Possible null reference assignment.
Build and Deploy to Azure Web App
Converting null literal or possible null value to non-nullable type.
Build and Deploy to Azure Web App
Possible null reference assignment.
Build and Deploy to Azure Web App: src/webapp01/Pages/Index.cshtml.cs#L22
Converting null literal or possible null value to non-nullable type.
Build and Deploy to Azure Web App: src/webapp01/Pages/Index.cshtml.cs#L22
Possible null reference assignment.
Build and Deploy to Azure Web App: src/webapp01/Pages/Index.cshtml.cs#L22
Converting null literal or possible null value to non-nullable type.
Build and Deploy to Azure Web App: src/webapp01/Pages/Index.cshtml.cs#L22
Possible null reference assignment.
Build and Publish Container Image / publish-image / publish-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: advanced-security/spdx-dependency-submission-action@169d22427d74f3faf93504e70b03eede8dab272a, docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/metadata-action@c299e40c65443455700f0fdfc63efafe5b349051, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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 and Publish Container Image / publish-image / publish-image
Please check that the "artifact-metadata:write" permission has been included
Build and Publish Container Image / publish-image / publish-image
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
Build and Publish Container Image / publish-image / publish-image
Snapshot successfully created at 2026-04-02T00:14:55.382Z
Build and Publish Container Image / publish-image / publish-image
{ "manifests": {}, "version": 0, "job": { "correlator": "publish-image", "id": "23877146811" }, "sha": "8b303fe7c77e0b3ed6d4d8ea4e6a77a47abdd13a", "ref": "refs/heads/main", "scanned": "2026-04-02T00:14:52.710Z", "detector": { "name": "spdx-to-dependency-graph-action", "version": "0.1.1", "url": "https://github.com/advanced-security/spdx-dependency-submission-action" } }

Artifacts

Produced during runtime
Name Size Digest
githubabcs-devops~gh-advsec-devsecops~GI2S66.dockerbuild
74.9 KB
sha256:e7ebab66e8f17d555e34d2e572fc49d86b0538e6c06c3e91b9b38c95c6be3489
githubabcs-devops~gh-advsec-devsecops~QYCK00.dockerbuild
37.4 KB
sha256:00b43eedcbc2310c8a01fc4ac7448ab3f7d6d7cb9da3b67384cf70b8c966240d
sarif
1.97 KB
sha256:7e1e7ab72a035449dfe4b3c687c09e3b82044bb968fa64bc87e848545535e207