Splunk AppDynamics

limit transformClassesWithAppDynamicsForXX to certain buildTypes (appdynamics-gradle-plugin)

Jerg_Weick
Explorer

subject: 

appdynamics-gradle-plugin

problem:

transformation runs on every buildType built

Hello,

i'm looking for a way to limit the class-transformation (gradle task is called "transformClassesWithAppDynamicsFor<buildType>") to certain build-types.

I'm aware of the flag 

adeum {
..
enabledForDebugBuilds = false
..
}

to limit transformation to release-builds, but that does not solve our problem, as we build several "release"-builds in our release-job(CI) but only 2 of them need to be instrumented and thus have it's classes transformed.

I wouldn't mind it at all if the transform-task would not take more than 6! minutes for a single build-type.

I'd appreciate any suggestion on how to achieve this.

regards,

Jerg

Labels (1)
0 Karma

Sergiu_Cosmin
Explorer

Hello, 

This should be possible now starting with 23.4.1. 

You have the option to disable based on build type, product flavor or variant. The properties you can use are exemplified below:  

adeum {
  disabledForBuildTypes = ["debug"]
  disabledForProductFlavors = ["app"] 
  disabledForVariants = ["appDebug"]
}
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...