fix: filter fortigate (#2579) #2280
mstopa-splunkci-lite.yaml
on: push
meta
26s
security-fossa-scan
3m 19s
Matrix: test-container
Scan docker image on CVEs
43s
Release
0s
Annotations
11 errors and 1 warning
|
security-fossa-scan
Process completed with exit code 1.
|
|
test-container (9.1.5, 29befd543def, false, true)
Failed to initialize container ghcr.io/splunk/splunk-connect-for-syslog/container3lite:develop
|
|
test-container (9.1.5, 29befd543def, false, true)
One or more containers failed to start.
|
|
test-container (9.2.2, d76edf6f0a15, false, false)
The job was canceled because "_9_1_5_29befd543def_false" failed.
|
|
test-container (9.2.2, d76edf6f0a15, false, false)
A task was canceled.
|
|
test-container (9.3.0, 51ccf43db5bd, true, false)
The job was canceled because "_9_1_5_29befd543def_false" failed.
|
|
test-container (9.3.0, 51ccf43db5bd, true, false)
A task was canceled.
|
|
test-ipv6-name-cache
Failed to initialize container ghcr.io/splunk/splunk-connect-for-syslog/container3lite:develop
|
|
test-ipv6-name-cache
One or more containers failed to start.
|
|
test-ipv4-name-cache
Failed to initialize container ghcr.io/splunk/splunk-connect-for-syslog/container3lite:develop
|
|
test-ipv4-name-cache
One or more containers failed to start.
|
|
meta
The following actions use a deprecated Node.js version and will be forced to run on node20: cycjimmy/semantic-release-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
THIRDPARTY
Expired
|
71.5 KB |
|
|
splunk~splunk-connect-for-syslog~4W33L3.dockerbuild
Expired
|
54.8 KB |
|