CLI exit codes

The Veracode CLI returns an exit code to indicate whether your command succeeded or triggered an error. Some commands might have multiple exit codes.

The following table lists the exit codes and their meaning.

Exit code	Command	Meaning
0	All commands	Command completed successfully.
1	All commands	Generic error.
2	All commands	Parser error. Check the command input and user permissions.
3	static scan and scan	The veracode static scan or veracode scan command completed successfully, but the scanned application did not pass policy.
4	package	The command completed unsuccessfully. Either no artifacts were created by the autopackager during the veracode package command, or the packaging process encountered build warnings. The behavior depends on whether you used the --strict flag: - Without --strict: No artifacts were found. Common causes include missing source files or failed compilation. - With --strict: The packaging completed with build warnings that should be reviewed and addressed.
4	package discover	The command did not complete successfully. No packageable artifacts were discovered, or the process produced warnings. Behavior depends on whether the --strict flag is used: - Without --strict: No artifacts were discovered. Common causes include missing source files, failed compilation, or missing build tool prerequisites. - With --strict: Warnings were produced, or some artifacts were not discovered. Review the reported issues.
5	package	Java packaging artifact contains no .class files. The veracode package command creates an artifact, but the artifact does not contain any compiled .class files.
6	package	Maven build succeeded but no artifact generated. The veracode package command using Maven completes successfully, but no artifact is generated.
7	package	Maven build failed and no artifact generated. The veracode package command using Maven fails during the build process, and no artifact is generated.
125	All commands	Out of memory.
126	All commands	Command failed. Check local system configuration.
127	All commands	Command not found. Check PATH configuration and command syntax.
128	All commands	Invalid argument. Retry the command.
130	All commands	Command terminated by user.