This message was deleted.

i did this very thing, but didnt ship it. you cant know if theres a build failure with old funcitonality. but what I did register with `sharedServices`:

val provider = target.gradle.sharedServices.registerIfAbsent("TimingsService", TimingsService::class) {
                val apkBuildDir = File(target.projectDir, "app/build/outputs/apk")
                this.parameters.apkDirExists.set(apkBuildDir.exists())
                this.parameters.projectName.set(target.name)
                this.parameters.taskNameList.set(target.gradle.startParameter.taskNames)
            }

if (registry is BuildEventListenerRegistryInternal) {
                registry.onOperationCompletion(provider)
            }

abstract class TimingsService :
    BuildService<TimingsService.Params>,
    BuildOperationListener,
    Closeable {

overridding:

override fun finished(buildOperation: BuildOperationDescriptor, finishEvent: OperationFinishEvent) {
        val result = finishEvent.result
        val details = buildOperation.details
        if (result is ExecuteTaskBuildOperationType.Result && details is ExecuteTaskBuildOperationDetails) {
            val name = details.task.project.name
            val duration = finishEvent.endTime - finishEvent.startTime
            if (result.skipMessage == null) {
                val total = moduleTimings[name]
                if (total != null) {
                    moduleTimings[name] = total + duration
                } else {
                    moduleTimings[name] = duration
                }
            } else {
                moduleCached[name] = result.skipMessage == TaskExecutionOutcome.FROM_CACHE.message
            }
        }

that's probably working because you don't have the config cache turned on?

we dont now. but this enabled the functionality with it turned on

config caching works decently well now if you're careful and keep all the module configs independent

oh nice. yeah sorely needed, configuration is like 30-1m of our build no matter what we change. someday we’ll revisit it 🙂

You should not use

BuilOperationListener

or an internal class. Here the proper way is documented: https://docs.gradle.org/current/userguide/build_services.html#operation_listener Make the build service implement

OperationCompletionListener

and register it with

BuildEventsListenerRegistry

. And if you need a hook for build finish, make the service also implement

AutoCloseable

. Those are the supported CC compatible ways.

finishevent on the

OperationCompletedListener

only gives you start and end time, not which module task ran

event.displayName

=>

"Task :foo:compileJava SUCCESS"

event.descriptor.displayName

=>

"Task :foo:compileJava"

event.descriptor.name

=>

":foo:compileJava"

cool. so we can parse out that format? niceeee. just have to parse the real module name out

If your build service implements

AutoCloseable

too, it will be triggered somewhen between the last task finished and the build finished. So you could record the start time of the first finished task and remember the task finish time of the last finished task and when the

close

is triggered, you know the last task happened, or you just take the time in the

close

method. You could also take the time when the listener is instaniated, but I'm not fully sure whether this will be after the first task finished or before it is started. By taking the task start time of the first task finished event you are on the safe side, especially if you want to record task execution time.