- Notifications
You must be signed in to change notification settings - Fork889
Ignoring unnecessarily generated surefire-report#518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Bert-R left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thanks for the improvement suggestion. However, one of the used flags is deprecated, see my other comment.
| cache:maven | ||
| -name:Build with Maven | ||
| run:mvn -B verify --file pom.xml | ||
| run:mvn -B verify --file pom.xml -Dsurefire.useFile=false -DdisableXmlReport=true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
The flagdisableXmlReport is deprecated, seethe documentation.
In our analysis, we observe that this target/surefire-report/ directory is generated but not later used during the CI build. Hence, we propose to disable generating this directory to save runtime.
The generation of this directory can be disabled by simply adding -Dsurefire.useFile=false -DdisableXmlReport=true to the mvn command.