Skip to content

/home/runner/.veracode/veracode.yml: no such file or directory #11

@dragospreutu

Description

@dragospreutu

In github action running [email protected] fails with:

DEBUG START

containerScan.ts - original scan command
scan --source ./ --type directory --format json --output results.json

DEBUG END

Scan command :../veracode-cli/veracode scan --source ./ --type directory --format json --output results.json
{"level":"warn","time":"2025-11-24T21:02:57Z","message":"failed to read config file: open /home/runner/.veracode/veracode.yml: no such file or directory\n"}

Credentials are validated by previous step without issues:
Run Veracode/[email protected]
VERACODE_API_ID and VERACODE_API_KEY is valid, Credentials expiration date - 2026-07-18T19:03:28.000+0000

Therefore I expect that veracode configure - failed to create .veracode/veracode.yml
Running in debug does not show any meaningful details for this issue:

DEBUG START

intall_cli.ts - command output
command output : Installing Veracode CLI...
Checking prerequisites...
Downloading veracode-cli_2.43.0_linux_x86.tar.gz...
==> copying files into "/home/runner/work/veracode/veracode-cli"

=============================== SUCCESS ========================================

The Veracode CLI is now installed!

If you do not have a Veracode API ID and Secret Key, navigate to
https://analysiscenter.veracode.com/auth/index.jsp#APICredentialsGenerator
to generate your API credentials and then configure them against the
Veracode CLI using the following command:

/home/runner/work/veracode/veracode-cli/veracode configure

DEBUG END

Installing Veracode CLI...
Checking prerequisites...
Downloading veracode-cli_2.43.0_linux_x86.tar.gz...
==> copying files into "/home/runner/work/veracode/veracode-cli"

=============================== SUCCESS ========================================

The Veracode CLI is now installed!

If you do not have a Veracode API ID and Secret Key, navigate to
https://analysiscenter.veracode.com/auth/index.jsp#APICredentialsGenerator
to generate your API credentials and then configure them against the
Veracode CLI using the following command:

/home/runner/work/veracode/veracode-cli/veracode configure

DEBUG START

containerScan.ts - original scan command
scan --source ./ --type directory --format json --output results.json

DEBUG END

Scan command :../veracode-cli/veracode scan --source ./ --type directory --format json --output results.json
{"level":"warn","time":"2025-11-24T21:02:57Z","message":"failed to read config file: open /home/runner/.veracode/veracode.yml: no such file or directory\n"}

Veracode Scan

INF: Vulnerability generation completed
INF: Secret detection scan completed
INF: Misconfiguration scan completed
INF: Policy evaluation completed
Error: Veracode CLI scan failed. Exit code: 3, Command: ../veracode-cli/veracode scan --source ./ --type directory --format json --output results.json
Note: Build failed due to break_build_on_error flag being set to true.
Scan command :../veracode-cli/veracode scan --source ./ --type directory --format table --output results.txt
{"level":"warn","time":"2025-11-24T21:03:33Z","message":"failed to read config file: open /home/runner/.veracode/veracode.yml: no such file or directory\n"}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions