Log error content captured during build
What does this MR do?
- When the code build runs, the error content/stack trace printed on the standard error stream is now logged instead of just
exit status
message. - When the user does not set SAST_JAVA_VERSION variable or sets unsupported Java version, added warning log on fallback version switch. Sample log message below:
[WARN] [Find Security Bugs] [2022-02-16T11:15:11Z] ▶ Java version not set in 'SAST_JAVA_VERSION' variable, using Java 8 as fallback.
Read more about setting Java Version at: https://docs.gitlab.com/ee/user/application_security/sast/#analyzer-settings
[WARN] [Find Security Bugs] [2022-02-16T11:23:29Z] ▶ Unsupported Java version set in 'SAST_JAVA_VERSION' variable, using Java 8 as fallback.
Read more about supported Java Versions at: https://docs.gitlab.com/ee/user/application_security/sast/#analyzer-settings
What are the relevant issue numbers?
gitlab-org/gitlab#322832 (closed)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Auto-DevOps template (also in CE) -
Job definition example -
CI Templates (to be removed) -
Vendored CI Templates (also in CE)
-
-
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer
Edited by Lucas Charles