Hi, a small update on this:
I improved the command in Perfkit. If you're interested, below you can find
the link to the PR. I also noticed that the task used for running
integration tests sometimes gets cached (locally, this doesn't happen on
Jenkins). The PR to this issue is also below[2].
Hi,
thanks for all the advice - much appreciated! During the mvn -> gradle
migration we just "translated" the existing mvn commands to gradle. We
definitely need to improve them in PerfKit now. I also like Scott's idea
about using the --profile flag. It would be awesome to utilize this in
Perfkit
+1 on only specifying the target that you need to build, You should use
'./gradlew -p path/to/java/project assemble' OR './gradlew
:project-artifact-name:assemble' to build the jars that you should need.
You can run these commands in a checked out version of your workspace and
validate that they
A few thoughts:
1. Gradle can intelligently build only the dependencies necessary for a
task, so it shouldn't build all of Python if the test suite, if you only
specify the task you're interested in. I'm not sure of the command for
"build all of the dependencies of my tests but don't run my
Hi Beam Devs,
currently PerfkitBenchmarker (a tool used to invoke performance tests) has
two phases that run gradle commands:
- Pre-build phase: this is where all the beam repo is build. This phase
is to prepare the necessary artifacts so that it doesn't happen when
executing tests.
