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!

Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...

This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

What You Read The Most: Splunk Lantern’s Most Popular Articles!

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...