SAST Scanning fails when setup as a multi-module Maven project.
Summary
SAST Scanning fails when setup as a multi-module Maven project.
Steps to reproduce
- Create a multi-module Maven project with two modules.
- Enable Dependency Scanning in
.gitlab-ci.yml
Example Project
https://gitlab.com/dansiviter/multi-module-failure
What is the current bug behavior?
It appears to be unable to locate a /tmp/app/target/spotbugsXml.xml file.
What is the expected correct behavior?
The testing completes and results returned.
Relevant logs and/or screenshots
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.269 s
[INFO] Finished at: 2018-07-02T11:02:26Z
[INFO] ------------------------------------------------------------------------
2018/07/02 11:02:26 open /tmp/app/target/spotbugsXml.xml: no such file or directory
2018/07/02 11:02:29 Container exited with non zero status code
ERROR: Job failed: exit code 1
See linked pipeline for example: https://gitlab.com/dansiviter/multi-module-failure/-/jobs/78759837
Output of checks
This bug happens on GitLab.com
Possible fixes
Unknown