-
Notifications
You must be signed in to change notification settings - Fork 154
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove building of frontend when running backend tests #1630
Comments
@dcshzj I have copied my comments over from #1631
|
I propose for the gradle build to be overhauled, with the following functions:
Existing to modify (?)
To discuss
Explanation for weird build process
|
@yhtMinceraft1010X Are you still working on this? |
I'm putting it on hold for now. But I hope to revisit it after finishing up #1625 |
Will wait for the following before continuing on this:
|
When running pure backend tests alone using gradlew test systemtest, the frontend is built before these tests. This is due to zipReport task being needed for compileJava. zipReport in turn relies on buildFrontend. The frontend is not used for these tests. It is wasteful to run buildFrontend when only the backend tests are being run. In addition, some other tasks and properties are scattered throughout the build.gradle file or have dependencies that could be pushed forward. This complicates maintenance. Let's remove the `test` and `systemtest` dependency on the frontend as well as re-order and consolidate some task properties and dependencies. This should make running either of them faster.
What feature(s) would you like to see in RepoSense?
Currently, when running
gradlew test
orgradlew test systemtest
, the frontend is built even though running the backend tests do not appear to require frontend in any way.I propose restructuring the dependencies in
build.gradle
such the frontend is not built when runningtest
orsystemtest
alone. (I.e. not part of build)The text was updated successfully, but these errors were encountered: