Reduced matrix concurrency to lower runner pressure:
max-parallel: 3
Optimized checkout for reliability and speed:
actions/checkout@v4 with fetch-depth: 1
Scope applies to PG14–PG18 smoke jobs on main/master/development and PRs.
Why
Prevent flaky CI behavior in development security scans.
Avoid intermittent matrix job instability (especially in later PG jobs) under higher parallel load.
Keep pipeline output actionable and predictable.
Validation
Scout scan step now progresses past the read-only SBOM/cache path issue.
Matrix workflow remains functionally identical while being less prone to infra-side checkout failures.
## Summary
This PR stabilizes CI security scanning and matrix reliability on the `development` branch.
## Changes Included
### 1) Docker Scout scan fix (development CVE workflow)
- Fixed Scout runtime error:
- `failed create to sbom folder: mkdir /root/.docker/scout: read-only file system`
- Kept Scout running with Docker socket access as root:
- `-u root`
- `-v /var/run/docker.sock:/var/run/docker.sock`
- Updated Docker auth config mount to be writable:
- from `:ro` to writable mount
- Result: Scout can now use local built images and write its internal cache/index data without failing.
### 2) PostgreSQL compatibility matrix stability improvements
- Reduced matrix concurrency to lower runner pressure:
- `max-parallel: 3`
- Optimized checkout for reliability and speed:
- `actions/checkout@v4` with `fetch-depth: 1`
- Scope applies to PG14–PG18 smoke jobs on `main/master/development` and PRs.
## Why
- Prevent flaky CI behavior in development security scans.
- Avoid intermittent matrix job instability (especially in later PG jobs) under higher parallel load.
- Keep pipeline output actionable and predictable.
## Validation
- Scout scan step now progresses past the read-only SBOM/cache path issue.
- Matrix workflow remains functionally identical while being less prone to infra-side checkout failures.
Replaced the use of Docker Hub secrets with a mounted local docker configuration file for authentication. Added a check to ensure the login config exists before running scans, preventing unnecessary failures. This change enhances flexibility and aligns with local environment setups.
Set `continue-on-error: true` for Docker Scout steps to ensure workflows proceed even if scans fail. Updated volume paths and environment variables for Docker config and credentials to improve scanning compatibility.
This update introduces a fallback mechanism for Docker Scout login when DockerHub credentials are unavailable, ensuring the workflow does not fail. It also replaces direct Docker config usage with temporary caching to improve flexibility and reduce dependency on runner environment setups.
Simplified the Docker Scout configuration logic by removing unnecessary checks and utilizing Docker's standard auth configuration. Updated environment variable usage and volume mounts to streamline the setup process for scanning containers.
This ensures the container runs with root user privileges, providing better compatibility and avoiding potential permission issues. The change affects the development workflow configuration for container CVE scanning.
Removed the read-only flag from Docker volume mounts in the container CVE scan workflow to allow modifications. Added `max-parallel` and `fetch-depth` configurations to the PostgreSQL compatibility matrix workflow for better performance and efficiency.
nessi
merged commit 21a8023bf1 into main2026-02-14 22:12:28 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
This PR stabilizes CI security scanning and matrix reliability on the
developmentbranch.Changes Included
1) Docker Scout scan fix (development CVE workflow)
failed create to sbom folder: mkdir /root/.docker/scout: read-only file system-u root-v /var/run/docker.sock:/var/run/docker.sock:roto writable mount2) PostgreSQL compatibility matrix stability improvements
max-parallel: 3actions/checkout@v4withfetch-depth: 1main/master/developmentand PRs.Why
Validation
-u rootflag to container CVE scan workflow