Slackbot
02/17/2023, 4:51 PMSlackbot
02/17/2023, 5:14 PMSlackbot
02/17/2023, 6:08 PMSlackbot
02/17/2023, 7:18 PMSlackbot
02/17/2023, 9:24 PMSlackbot
02/17/2023, 9:52 PMSlackbot
02/18/2023, 3:45 AMSlackbot
02/18/2023, 11:03 AMSlackbot
02/18/2023, 8:32 PMSlackbot
02/19/2023, 2:44 PMSlackbot
02/19/2023, 4:09 PMSlackbot
02/19/2023, 9:03 PMSlackbot
02/20/2023, 8:21 AMFilip Daca
02/20/2023, 10:04 AM7.5.1
.
• among used plugins, we have scala
, java-library
and recently java-test-fixtures
Every time test
task is executed, jar
task is also triggered for this and dependent subprojects. Report states jar
"must run before" test
. How can we set it up not to require jar
, but only compiled classes
/ testClasses
?
This is impacting our performance and cost, because we're running several stages independently in CI, and want to run jar
only once and only when it's needed. jar
is not cacheable and it's not worth cacheing. Right now compiled classes are pulled from cache, and jar is generated anyway for no good reason.
I have tried using -x jar
but it is still expecting dependent project jars to be there.Slackbot
02/20/2023, 10:27 AMSlackbot
02/20/2023, 2:44 PMSlackbot
02/20/2023, 3:28 PMSlackbot
02/20/2023, 4:37 PMSlackbot
02/20/2023, 9:22 PMSlackbot
02/21/2023, 12:14 AMSlackbot
02/21/2023, 7:02 AMSahana M K
02/21/2023, 9:50 AMProcess 'Gradle Test Executor 2' finished with non-zero exit value 2551192 This problem might be caused by incorrect test process configuration. 1193 Please refer to the test execution section in the User Manual at https://docs.gradle.org/6.8.4-20210419220000+0000/userguide/java_testing.html#sec:test_execution
Slackbot
02/21/2023, 11:36 AMSlackbot
02/21/2023, 3:00 PMSlackbot
02/21/2023, 9:24 PMEsa Firman
02/22/2023, 2:19 AMSlackbot
02/22/2023, 12:09 PMSlackbot
02/22/2023, 1:37 PMSlackbot
02/22/2023, 3:55 PMSlackbot
02/22/2023, 10:53 PM