ganachoco
11/07/2023, 12:59 AMPredictive Test Selection
on my android project.
But it seems to require JUnit5 to enable Predictive Test Selection
.
And android test frameworks (robolectric or android instrumentation tests) are still based on JUnit4.
Is there migration guide to use Predictive Test Selection
for android project?Slackbot
11/09/2023, 1:25 PMRené
11/21/2023, 10:38 PMThe build cache configuration of the root build differs from the build cache configuration of the early evaluated ':build-conventions', ':build-tools', ':build-tools-internal' included builds. It is recommended to keep them consistent, see here .
We apply our build cache configuration via an init script. That worked well before. When debugging, we see these events resolved from the export api
id: 0
event: BuildEvent
data: {"timestamp":1700602606852,"type":{"majorVersion":1,"minorVersion":1,"eventType":"BuildCacheConfiguration"},"data":{"local":{"type":"directory","className":"org.gradle.caching.local.DirectoryBuildCache","config":{"location":"/opt/buildkite-agent/.gradle/caches/build-cache-1","removeUnusedEntriesAfter":"7 days"},"push":true,"enabled":true},"remote":{"type":null,"className":null,"config":null,"push":null,"enabled":false},"buildCacheEnabled":true,"buildPath":":build-conventions"}}
id: 1
event: BuildEvent
data: {"timestamp":1700602608074,"type":{"majorVersion":1,"minorVersion":1,"eventType":"BuildCacheConfiguration"},"data":{"local":{"type":"directory","className":"org.gradle.caching.local.DirectoryBuildCache","config":{"location":"/opt/buildkite-agent/.gradle/caches/build-cache-1","removeUnusedEntriesAfter":"7 days"},"push":true,"enabled":true},"remote":{"type":null,"className":null,"config":null,"push":null,"enabled":false},"buildCacheEnabled":true,"buildPath":":build-tools"}}
id: 2
event: BuildEvent
data: {"timestamp":1700602612227,"type":{"majorVersion":1,"minorVersion":1,"eventType":"BuildCacheConfiguration"},"data":{"local":{"type":"directory","className":"org.gradle.caching.local.DirectoryBuildCache","config":{"location":"/opt/buildkite-agent/.gradle/caches/build-cache-1","removeUnusedEntriesAfter":"7 days"},"push":true,"enabled":true},"remote":{"type":null,"className":null,"config":null,"push":null,"enabled":false},"buildCacheEnabled":true,"buildPath":":build-tools-internal"}}
id: 3
event: BuildEvent
data: {"timestamp":1700602628253,"type":{"majorVersion":1,"minorVersion":1,"eventType":"BuildCacheConfiguration"},"data":{"local":{"type":null,"className":null,"config":null,"push":null,"enabled":false},"remote":{"type":"Gradle Enterprise","className":"com.gradle.enterprise.gradleplugin.internal.a.b","config":{"Allow untrusted server":"false","Cache path":"cache","Allow insecure protocol":"false","Use ExpectContinue":"false","Gradle Enterprise server":"<https://ge.acme.co>","Use username/password":"true","Build cache server":"<https://gradle-enterprise.elastic.co>","Use access key":"false"},"push":true,"enabled":true},"buildCacheEnabled":true,"buildPath":":"}}
before switching to the Gradle Enterprise connector we saw this "correct" appearing setup:
id: 0
event: BuildEvent
data: {"timestamp":1700052651320,"type":{"majorVersion":1,"minorVersion":1,"eventType":"BuildCacheConfiguration"},"data":{"local":{"type":null,"className":null,"config":null,"push":null,"enabled":false},"remote":{"type":"HTTP","className":"org.gradle.caching.http.HttpBuildCache","config":{"allowUntrustedServer":"false","authenticated":"true","useExpectContinue":"false","allowInsecureProtocol":"false","url":"<https://ge.acme.co/cache/>"},"push":true,"enabled":true},"buildCacheEnabled":true,"buildPath":":build-conventions"}}
id: 1
event: BuildEvent
data: {"timestamp":1700052652095,"type":{"majorVersion":1,"minorVersion":1,"eventType":"BuildCacheConfiguration"},"data":{"local":{"type":null,"className":null,"config":null,"push":null,"enabled":false},"remote":{"type":"HTTP","className":"org.gradle.caching.http.HttpBuildCache","config":{"allowUntrustedServer":"false","authenticated":"true","useExpectContinue":"false","allowInsecureProtocol":"false","url":"<https://ge.acme.co/cache/>"},"push":true,"enabled":true},"buildCacheEnabled":true,"buildPath":":build-tools"}}
id: 2
event: BuildEvent
data: {"timestamp":1700052654020,"type":{"majorVersion":1,"minorVersion":1,"eventType":"BuildCacheConfiguration"},"data":{"local":{"type":null,"className":null,"config":null,"push":null,"enabled":false},"remote":{"type":"HTTP","className":"org.gradle.caching.http.HttpBuildCache","config":{"allowUntrustedServer":"false","authenticated":"true","useExpectContinue":"false","allowInsecureProtocol":"false","url":"<https://ge.acme.co/cache/>"},"push":true,"enabled":true},"buildCacheEnabled":true,"buildPath":":build-tools-internal"}}
id: 3
event: BuildEvent
data: {"timestamp":1700052656465,"type":{"majorVersion":1,"minorVersion":1,"eventType":"BuildCacheConfiguration"},"data":{"local":{"type":null,"className":null,"config":null,"push":null,"enabled":false},"remote":{"type":"HTTP","className":"org.gradle.caching.http.HttpBuildCache","config":{"allowUntrustedServer":"false","authenticated":"true","useExpectContinue":"false","allowInsecureProtocol":"false","url":"<https://ge.acme.co/cache/>"},"push":true,"enabled":true},"buildCacheEnabled":true,"buildPath":":"}}
This appears to be a bug in the connector api. Is there a workaround or a fix for this?René
11/21/2023, 10:40 PMritesh singh
11/25/2023, 11:36 AMManuel Nakamurakare
11/27/2023, 7:26 PMCharbel Sadaka
12/05/2023, 7:27 AMKyle Lehman
12/07/2023, 7:52 PMprepareKotlinBuildScriptModel
task.Gabriel Feo
12/08/2023, 7:46 PMConan Bee
12/15/2023, 10:04 AMvoid configureA(Configuration c, List l) {
c.resolutionStrategy { ResolutionStrategy rs ->
List ll = []
rs.eachDependency {details ->
if (details.requested.name == "groovy") {
details.useVersion('3.0.8')
println details.requested.name
}
ll.add(details.requested.name)
project.logger.lifecycle("+++++++++ll: ${ll}++++++++++")
}
project.logger.lifecycle "==========ll: ${ll}=========="
}
project.logger.lifecycle "==========l: ${l}=========="
}
void configureInit() {
List l = []
project.configurations.configureEach {
configureA(it, l)
}
project.logger.lifecycle "########l: ${l}#########"
}
Vinay Potluri
01/23/2024, 12:57 AM--scan
flag for every command. How do I enable this flag by default for all commands within the project ?
2. Can I enable this for a set of tasks so that I have a single build scan for required tasks combined ?Sergey Chernov
01/26/2024, 11:33 AMJean Helou
02/02/2024, 3:09 PM❯ git diff
diff --git a/.mvn/gradle-enterprise.xml b/.mvn/gradle-enterprise.xml
index 11ead2618b..b91bda1be4 100644
--- a/.mvn/gradle-enterprise.xml
+++ b/.mvn/gradle-enterprise.xml
@@ -11,9 +11,9 @@
<buildScan>
<backgroundBuildScanUpload>#{isFalse(env['CI'])}</backgroundBuildScanUpload>
<!-- Always publish build scans for CI, only if requested locally -->
- <publish>#{env['CI'] == null ? 'ON_DEMAND' : 'ALWAYS'}</publish>
+ <publish>#{env['CI'] == null ? 'ALWAYS' : 'ALWAYS'}</publish>
<capture>
- <goalInputFiles>false</goalInputFiles> <!-- To be enabled locally when debugging goal caching or if we want to enable predictive test selection -->
+ <goalInputFiles>true</goalInputFiles> <!-- To be enabled locally when debugging goal caching or if we want to enable predictive test selection -->
<buildLogging>false</buildLogging> <!-- disabled by default for privacy and performance, to be discussed -->
<testLogging>false</testLogging> <!-- disabled by default for privacy and performance, to be discussed -->
</capture>
any idea what I'm missing here ?CristianGM
02/12/2024, 2:36 PMPhilip W
04/03/2024, 8:04 AMplugins {
id "com.gradle.develocity" version "3.17"
}
develocity {
buildScan {
termsOfUseUrl = '<https://gradle.com/terms-of-service>'
termsOfUseAgree = 'yes'
}
}
Jonathan kernan
04/03/2024, 3:51 PMJörgen Andersson
04/08/2024, 5:42 PMZak Taccardi
04/09/2024, 12:44 AMŁukasz Wasylkowski
04/15/2024, 11:30 AM--scan
it's now an opt-out via --no-scan
or publishing { onlyIf { false } }
to get back to the old behavior. Not a big deal, but there's no mention of that anywhere in the release notes, so we upgraded a bunch of repos only to have to go and adjust all the scripts to the old behavior.
Then there's 3.17.1 version which allows muting obscure deprecation warnings, apparently from transitive dependencies (why would they pull GE, I don't know). But the release notes say [NEW] Support muting Gradle Enterprise deprecation warnings coming from transitive dependencies
, but how do I do that?TrevJonez
04/17/2024, 5:17 PMAudrius
05/07/2024, 3:31 PMcom.gradle.develocity
scan publishing?
I am migrating to com.gradle.develocity
. But we started to get errors:
Publishing build scan...
Publishing build scan failed due to network error 'java.net.SocketTimeoutException: Read timed out' (2 retries remaining)...
Publishing build scan failed due to network error 'java.net.SocketTimeoutException: Read timed out' (1 retry remaining)...
A network error occurred
(this fails just sometimes, most of the time it passes on one of retries)
This is kinda expected, as we have very slow connection. But it is working fine with the old gradleEnterprise pluging, so I assume, that there was some network connectivity/timeout related change gradleEnterprise -> develocity?Shailesh
05/08/2024, 11:27 AMM K Matthur
05/08/2024, 1:43 PMM K Matthur
05/08/2024, 1:45 PM> Task :compileJava FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':compileJava'.
Could not find tools.jar. Please check that /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.412.b08-2.el8.x86_64/jre contains a valid JDK installation.* Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/5.6.4/userguide/command_line_interface.html#sec:command_line_warnings BUILD FAILED in 1s 1 actionable task: 1 executed
Josh Friend
05/10/2024, 1:14 PMSergey Chernov
05/29/2024, 3:12 PM2023.4.6
)?
What I expect is test displayName
in the execution report (see example of test execution in the IDEA-first screenshot).
But actually it's just numerated losing actual argument toString representation (see the second screenshot).
There was a related issue in the Gradle Build Tool https://github.com/gradle/gradle/issues/5975 but in this case we are talking about DevelocityFelix de Souza
06/03/2024, 6:24 PMKyle Lehman
06/14/2024, 7:35 PMBrais Gabín Moreira
06/28/2024, 8:57 AMRené
06/28/2024, 12:33 PMperformance/configuration
data via develocity api? In addition to our weekly build cache validation I want to add a configuration cache validation ci job to verify our build keeps being configuration cache compatible and hits the configuration cache. We're in the process of migrating but its a longer complex journey so I would like to have sanity checks in ci until we can enable it by default and not having incompatibilities creeping back into our build over time. Seems for now I need to parse the build output till that api is available?